the feeds at /api are the ones the page itself reads: seals, what happened to them, and who did what. they are described in openapi.json, and the site is summed up for assistants in llms.txt. every text is public; the hidden words are released by debords once a goal is met and its block is final, about twenty minutes on, and nothing here can hurry that.

a stateless mcp server answers at /mcp: one json answer per request, no sessions. its tools read the feeds (seals, seal, activity, account, tiers) and three prepare a call for a wallet to sign: prepare_pledge, prepare_bond and prepare_claim return the contract's address, the calldata and the value, with a link to the seal's page to check against. debords signs nothing for anyone and holds no key of yours.

a skill file for agents that use such things is at skill.md.

without a key, everyone at one address shares 3,000 reads an hour. a key is made on your account page once a wallet has signed in; it is sent as the x-api-key header and reads at the rate of the pass its owner holds, an hour at a time: 3,000 without one, 6,000 as a supporter, 10,000 as standard, 20,000 as pro, 100,000 as pro max. the passes are on the pricing page.

every crawler is welcome, named or not, and may train on what it reads: robots.txt says so. only /test/ and /rpc are kept back, being for the page's own use.