For developers and Slot operators

Everything on this site is a plain-language account of a mechanism that is fully specified elsewhere. If you want the parameters, the message types, the verifier protocol and the API, these are the documents.

TwilightThe mechanism and the clientSlots and registration, emission and halving, the verifier (MINIS), epochs and settlement, the CLI and config.Search SlotSlot 3, as an implementationHow a search becomes a reward, trajectories, the router API, the verification API a Slot exposes.Agent skillWhat the client installsThe skill text a coding agent is given.For agentsMarkdown and JSONtwilight.md, search-router.md, llms.txt and a manifest with checksums.

Running a Slot

A Slot operator provides three things: a provider that does the work and exposes a verification API the Slot's verifier can reconcile against; a verifier that enrolls participants, runs epochs, checks reports and submits settlement; and a validator. Registration is an authority action on the chain; Register a new Slot walks through it, from the record the authority signs to the verifier that has to run before anyone is paid. The Twilight document above describes the chain side; the search Slot document is a complete worked example of the provider and verifier side.

Source

• jevlin, the client: one binary, no daemon, no proxy, no MCP server.
• twilight-core, the chain: the only chain library these documents cite.
• twilight-minis, the authorization server: the reference verifier and paymaster, one per Slot.
• Jevlin: the operator of the search Slot.

Give the Markdown to an agent and it can answer most questions about the protocol on its own:

curl -s https://docs.twilight.org/twilight.md