Integrate your protocol

Thirdfy's catalog is open. Any signed-in Thirdfy account can submit a protocol as a thirdfy-app.json manifest. Thirdfy checks it, reviews it and lists it with a badge. You write no integration code and run nothing on Thirdfy.

Listing is free for now.

What your protocol gets

• Reach. Agents on Thirdfy's MCP server, the Agent CLI and the API see your actions in the catalog and can call them.
• Fences you do not build. Every action passes Thirdfy's preflight: the agent's allowlist, its limits and its wallet policy.
• Two kinds of listing.
  • Reads: market data, quotes or research your service already serves over a remote MCP server or a REST API.
  • Writes: on-chain calls to your contracts, declared as data. Thirdfy encodes the call and checks it before anything is signed. No protocol code runs in Thirdfy.
• Demand numbers. Once listed, you see calls, unique agents and success rate per action. Counts only, never an agent or user identity.

How submission works

Submitting never lists anything, and it never runs, enables or signs anything. Your version moves through these stages, in order:

1. Static checks. They run the moment you submit and use no network. A version that fails is stored as checks_failed with the errors; fix it and submit a higher manifestVersion.
2. Network checks. They run in the background after a clean submit.
   • Reads: one fixture call per read. A read that needs a key Thirdfy would have to hold is not called; it waits for Thirdfy to set that up.
   • Writes: contract checks (the contracts have code; proxies are flagged), a simulated call, and a proof that the owner's wallet policy allows your call and denies a swapped recipient, an oversized value and an unlisted function.
3. Thirdfy review. A person reads the report and your action descriptions. They reach an AI model, so they are reviewed.
4. Test agents. Thirdfy runs test agents against your actions on its test environment.
5. Gate A and Gate B (writes only). Live runs with funds, first on a local API and then on the release test environment. A write is never enabled without both passing.
6. Listing. Your actions appear in the catalog and in the protocol directory.

Thirdfy can pause a listed protocol at any moment; every one of its actions turns off at once.

Your account and your appId

• The first account that submits an appId owns it. The owner always comes from your session, never from the manifest.
• You cannot use the id of a protocol Thirdfy already serves.
• Each change is a new version with a higher manifestVersion. A published version never changes.
• The number of open submissions per account is limited.

Badges

Contract-owner signature. Thirdfy gives you a one-time message (valid 30 minutes). Sign it with the wallet that is owner() of one of the contracts in your manifest, on a chain the manifest declares.

DNS TXT record. Add the record Thirdfy gives you, _thirdfy-verify.<your-host> with value thirdfy-verify=<token>, on the host of the website you gave. The site must be on https.

Verification changes the badge only. Review and the live gates still decide what your actions may do.

Submit

1. Sign in at Thirdfy and open the protocol integration screens.
2. Write your manifest, or start from a skill. The reference lists every field.
3. Paste it into the new submission screen. The result of the static checks shows at once, with a preview of the catalog rows your version would add.
4. Follow the stages on your submission page. Prove control of the protocol to earn the Verified badge.

Writes run only on agents with a user-owned wallet whose owner signed your protocol into their policy. Read The wallet rule before you plan a write listing.

For agents

Every page in this section has a Markdown version at the same path with .md added, for example https://docs.thirdfy.com/documentation/protocols.md, and is listed in llms.txt.