Use DEBYKO from AgentKit
An AgentKit agent can call DEBYKO today, with no DEBYKO provider installed. DEBYKO is listed on
Agentic Market, and AgentKit ships a generic
x402 provider that discovers a listed service, reads the 402, and pays it. The payable routes and
prices are the ones on that listing: POST /v2/snapshots at 0.005 USDC, POST /v2/screen at 0.01 USDC,
POST /v2/snapshots/history at 0.02 USDC, and POST /v2/candles at 0.005 USDC, on Base (eip155:8453), native USDC.
That path is how an agent finds the API and pays for a call.
Typed actions
Section titled “Typed actions”A DEBYKO action provider adds three typed actions on top of that path. Discovery and payment stay with the
built-in x402 provider and the listing. What the typed actions add is a description the model can follow, DQL
guidance on the screen action, the error body as DEBYKO wrote it (code, message, hint), a Bearer key that
never falls back to a payment, and a per-call cap that is checked before anything is signed.
| action | request | price |
|---|---|---|
debyko_snapshots |
POST /v2/snapshots |
0.005 USDC |
debyko_screen |
POST /v2/screen |
0.01 USDC |
debyko_history |
POST /v2/snapshots/history |
0.02 USDC |
debyko_screen takes a DQL query, a limit and include_unknown. The query is DQL, and the names in it come from
the catalogue. The guide is DQL. Snapshot and history inputs are the fields those requests already
accept. Every value comes back with its venue, its age and its status. A stale value is withheld: it is not returned
as the number.
The provider is staged in this repository at clients/agentkit-action-provider/, in the shape of
typescript/agentkit/src/action-providers/debyko/, so it can be copied into AgentKit. It is not published, and
being shaped for that tree is not the same as AgentKit having accepted it.
Paying and a key
Section titled “Paying and a key”Without a key, the provider uses AgentKit’s own x402 client. The default cap is 0.05 USDC per call. An offer above
it, on another network, for another asset, or in a PAYMENT-REQUIRED header that cannot be read, is refused before
a signature. A 402 also lists 30-day plan prices; those sit above the cap and are not signed. The call price is.
DEBYKO answers a paid request before the payment settles, so the success usually has no settlement header. The provider returns the JSON and does not invent a transaction hash. When a settlement header is present, it is parsed.
With apiKey, the request sends Authorization: Bearer and does not enter x402. If that request fails, the
DEBYKO error is returned. It is not retried as a payment.
An agent that wants tools rather than these three actions uses the remote MCP server. That is Connect an AI agent. The MCP server authorises with a key or with OAuth, and paying per call stays the direct API path above.