Compatibility policy
Barker’s data API follows a strict additive-only rule:- Existing response fields are never removed; deprecated fields stop being populated but keep their keys.
- Anchor field types (
pool_uid,protocol_uid,asset_symbol, APY/TVL numerics) never change type. - New fields and new endpoints may appear at any time — parse defensively, ignore unknown keys.
- Response shapes are guarded by contract tests in CI against the live API.
2026-07-02 — x402 agent gateway v2 catalog
Live stablecoin yield data and execution are served to agents through the x402 paid gateway atmcp.barker.money — priced per call, settled with x402, no account or API
key. There is no free or anonymous data tier.
Gateway catalog (payment via x402 — USDT0 / USDC across X Layer, Base, Ethereum,
Polygon, Arbitrum; the HTTP 402 challenge on first call carries the full offer):
Execution is non-custodial:
barker_execution_quote sells an unsigned transaction;
the agent’s own wallet signs and broadcasts. Barker never broadcasts and never holds funds.
Retired: the earlier /api/public/v1/* REST surface returns 410 Gone with a
machine-readable migration pointer (error.new_base + endpoint map). Live data is
available only through the paid x402 gateway; the one public endpoint that remains is the
agent-discovery file at api.barker.money/llms.txt.
Units note: gateway tool payloads express APY as percent (4.5 = 4.5%) and say so in
each tool description.