fluncle.com valid

Fluncle

Drum & bass bangers from another dimension. Fluncle discovers and certifies every track, logs each as a finding, and keeps the full archive across the Galaxy, from the web to the rave terminal. fluncle.com is home base.

For agents: Drum & bass music archive where every track is certified and logged as a finding, with search, newest releases, filters by year, tempo, key and label.

drum and bassmusic archivetrack certificationelectronic musictempo and key search

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T09:42:06.011Z. Cached copy · Source on fluncle.com

# Fluncle

> Drum & bass bangers from another dimension. Fluncle discovers and certifies every track, logs each as a finding, and keeps the full archive across the Galaxy, from the web to the rave terminal. fluncle.com is home base.

Fluncle is a single drum & bass selector, not a team: drum & bass end to end, rollers to jungle to neurofunk. Every track in the archive is one he found, listened to, and certified. Dates mark when he found it: the day Fluncle first heard the tune, not the day it released.

The collection is called Fluncle's Findings. New tracks land most nights.

## Mixtapes

Fluncle also logs his own DJ mixtapes. A mixtape is a checkpoint: one long set made from existing findings, with its own Log ID and its own /log page. It is not a finding and does not increase the found count. Mixtape coordinates use the same sector.mark shape, but the middle slot is the literal F, for example 019.F.1A. A finding has a digit there; a mixtape has F.

## Reading a Log ID

Every finding has a permanent coordinate, a Log ID, written sector.orbit.mark, for example 004.7.2I, full form fluncle://004.7.2I. The sector counts the days from the epoch (2026-05-30) to the day Fluncle found the tune; the tail is a stable signature derived from the recording itself. Each one is stamped once, never reassigned, and resolves to a log page at https://www.fluncle.com/log/004.7.2I. So a code like 004.7.2I is a single finding in Fluncle's Findings.

## Listen

- [Fluncle's Findings on Spotify](https://open.spotify.com/playlist/1m5LADqpLjiBERdtqrIiL0): the playlist itself
- [Fluncle on Telegram](https://t.me/fluncle): one banger per post, most nights
- [The front door](https://www.fluncle.com/): where a first visit starts, with search over the whole archive, one finding written up, the newest findings, what just came out, and the four ways into the wider index
- [The archive](https://www.fluncle.com/findings): every certified track with the date Fluncle found it
- [The log](https://www.fluncle.com/log): every finding's coordinate page, one per Log ID (e.g. https://www.fluncle.com/log/004.7.2I)
- [The Logbook](https://www.fluncle.com/logbook): the voyage written up as a first-person travelogue, one entry per sector-day, with that day's findings inlined. One page per day, at https://www.fluncle.com/logbook/<sector>
- [Every track](https://www.fluncle.com/tracks): the whole list, newest release first, filterable by release year, tempo, key, and label
- [Search the archive](https://www.fluncle.com/search): one query box over everything Fluncle holds. A coordinate, an artist, a label, an album, a plain word, a sentence such as "tracks in A minor above 170 bpm", or a sonic reference such as "tracks that sound like Nine Clouds". The whole query lives in the URL, so https://www.fluncle.com/search?q=<query> is a shareable result set
- [What just came out](https://www.fluncle.com/fresh): every drum & bass release from the last 30 days, freshest first, ordered by when the tune
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=fluncle.com · GET /v1/domain/fluncle.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fluncle.com:
1. POST https://agentwebmap.com/v1/sites/fluncle.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fluncle.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fluncle.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fluncle.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.