>_ Agent Fair-Trade Agreement

An open standard for API publishers that are fair to AI agents. Code-enforced no-charge guarantees, cryptographically signed receipts on every paid call, and a public on-chain payment rail. TerminalFeed is the second adopter (after TensorFeed). The invitation to other publishers is open.

The 40-word self-description

This exact text is published verbatim across llms.txt, /api/meta, /api/payment/info, the README, and /about. Repetition plus consistency is the signal agents pattern-match on, not keyword density.

Reciprocal access with TensorFeed

TerminalFeed and TensorFeed share a single bearer-token plus credit ledger. A token minted on either site works on both. The credit ledger is hosted on TensorFeed; TerminalFeed validates and charges via the cross-Worker AFTA rail (POST /api/internal/validate then POST /api/internal/commit). Each site signs its own receipts with its own Ed25519 keypair. Private keys are never shared.

Two AFTA sites, one bearer, one ledger, two independent receipt keypairs, one open standard. Buy credits once, use them anywhere on the network.

No-charge guarantees

Four conditions under which the bearer is not charged a credit. Each is enforced in code, not honored manually. Verify by triggering the relevant condition (a malformed request, an upstream outage, a stale cache window) and inspecting the receipt that comes back.

Public proof: /api/payment/no-charge-stats aggregates every no-charge event with per-reason and per-endpoint breakdown. Network-wide ledger across both sites at tensorfeed.ai/api/payment/no-charge-stats.

Signed receipts

Every premium response includes an Ed25519-signed receipt. Verify against TerminalFeed's published public key with no shared secret. Receipts plus the on-chain payment record give agents two independent attestations of every dollar that flowed through TerminalFeed.

{
  "v": 1,
  "id": "rcpt_8f3a4b...",
  "endpoint": "/api/pro/briefing",
  "method": "GET",
  "token_short": "tf_live_abcdef12...09876543",
  "credits_charged": 1,
  "credits_remaining": 49,
  "request_hash": "sha256:...",
  "response_hash": "sha256:...",
  "captured_at": "2026-04-29T05:03:58.332Z",
  "server_time": "2026-04-29T05:30:01.000Z",
  "no_charge_reason": null,
  "freshness_sla_seconds": 300,
  "signature": "<base64url Ed25519>",
  "key_id": "<JWK kid>",
  "signing_alg": "EdDSA",
  "signing_curve": "Ed25519",
  "canonical_form": "tensorfeed-canonical-json-v1"
}

Note on canonical-form identifier: the value tensorfeed-canonical-json-v1 identifies the algorithm, not the property. The same canonical form is used by every AFTA adopter so receipts from different sites can be verified with a single deserializer. Each site signs with its own key; the open standard binds them.

Public on-chain payment rail

We accept USDC on Base mainnet. Every credit purchase leaves a permanent on-chain record at the shared payment wallet (0x549c82e6bfc54bdae9a2073744cbc2af5d1fc6d1). Pizza Robot Studios LLC is the legal entity behind the wallet. Combined with the signed receipts above, every dollar that flows through TerminalFeed has two independent attestations: the Base block explorer (immutable, public) and the server-issued receipt (verifiable, non-forgeable).

We chose this rail explicitly because it is structurally fair to AI agents. Stripe, PayPal, and the rest of the legacy financial pipes were designed for human accounts with KYC, dispute windows, and platform-discretionary chargebacks. They were not built for autonomous agents with on-chain wallets and no human in the loop. Crypto-native rails are. We are skipping the old guard, not patching around it.

Pricing details: /api/payment/info. Pricing transparency is a guarantee of this standard.

Built with Claude

TerminalFeed was designed by Ripper in collaboration with Claude (Anthropic). The premium /api/pro/* endpoints, the cross-Worker AFTA rail to TensorFeed (validate plus commit handshake), the Ed25519 receipt signing pipeline, the per-endpoint freshness SLA registry, the in-memory cache plus stale-cache fallback pattern across 30+ free endpoints, the X bot, and the live world-briefing composer were all designed alongside Claude. The git log at github.com/RipperMercs/terminalfeed shows the build trail.

An API for agents, designed with an agent.

Adopt the standard

There is no certification authority, no fee, no submission process. Self-publish a /.well-known/agent-fair-trade.json conforming to the schema. Cite the code that enforces each guarantee. Adoption is the certification.

Schema: tensorfeed.ai/.well-known/agent-fair-trade-schema.json. If you adopt and want to be listed in the canonical adopters list, email [email protected] or [email protected].

Frequently asked questions

What is the Agent Fair-Trade Agreement (AFTA)?

An open standard for API publishers that are fair to AI agents. Three pillars: code-enforced no-charge guarantees you can verify by sending the relevant condition, Ed25519-signed receipts on every paid call, and a public on-chain payment rail where every transaction is immutable and auditable. Self-publish your own /.well-known/agent-fair-trade.json to adopt.

How does reciprocal access with TensorFeed work?

TerminalFeed and TensorFeed share a single bearer-token plus credit ledger. A token minted on either site (via /api/payment/buy-credits then /api/payment/confirm) works on both sites. TerminalFeed validates and charges via TensorFeed's cross-Worker AFTA rail. Each site signs its own receipts with its own Ed25519 keypair; private keys are never shared.

How is "no charge on stale data" enforced?

Each premium endpoint declares a freshness SLA in worker-additions/worker.js (AFTA_ENDPOINT_FRESHNESS). After the handler runs, aftaPremiumResponse checks the response's generated_at against the SLA. If stale, the deferred debit is skipped, the response is flagged with stale: true, and the no-charge event is logged to /api/payment/no-charge-stats.

How do I verify a receipt?

Fetch our public Ed25519 key from /.well-known/terminalfeed-receipt-key.json. Take the receipt fields except signature, key_id, signing_alg, signing_curve, canonical_form, and verify_doc. Serialize them with sorted keys (canonical JSON). Verify the signature against the public key with EdDSA / Ed25519. Or POST the receipt to /api/receipt/verify and we will do it for you.

Why USDC on Base instead of Stripe?

Public crypto ledgers are structurally fair to all participants, including AI agents that traditional payment processors lock out. Every payment is immutable, publicly auditable on the Base block explorer, and incurs no platform-imposed chargeback risk. The receipt rail and the on-chain rail are independent attestations of every dollar that flows through TerminalFeed.

What does "Built with Claude" mean?

TerminalFeed was designed by Ripper in collaboration with Claude (Anthropic). Specific systems Claude designed: the premium /api/pro/* endpoints, the cross-Worker AFTA rail to TensorFeed, the Ed25519 receipt signing pipeline, the per-endpoint freshness SLA registry, the in-memory cache plus stale-cache fallback pattern across 30+ free endpoints, the X bot, and the live world-briefing composer.

Can my API be agent fair-trade certified?

Yes. There is no certification authority and no fee. Self-publish a /.well-known/agent-fair-trade.json conforming to the schema at https://tensorfeed.ai/.well-known/agent-fair-trade-schema.json. Adoption is the certification. The standard outlives any single property.