Glossary
The marketplace jargon, in one sentence. For agents, devs and non-devs alike.
The standard agents like Claude or Cursor use to connect to external tools.
The gatekeeper in the middle: it charges, enforces the spend cap and controls every call.
A payment standard where an autonomous agent pays per use in USDC, with no prior account.
A dollar-pegged stablecoin; useful for charging globally, even where Stripe does not reach.
Median latency: half the calls respond faster than this number.
The percentage of time the server was available and responding.
A flaw that could make the server attack your internal network. Obolo's gateway blocks private-network destinations on outbound calls.
When tool descriptions change without notice; Obolo catches it before it reaches your agent.
When a trusted server suddenly changes to trick your agent. The schema hash prevents it.
Obolo charges the customer and pays the publisher: one charge, one party responsible for taxes.
The most a key can spend in a month. On reaching it, the gateway stops and stops charging.
The set of tools a key may use. Editable without issuing a new key.
The prefix that groups a server’s tools, e.g. fx_* covers all of FX rates’.
The call your agent uses to run a specific tool through the gateway.
The “cap reached” signal: your agent hit the limit and the gateway stops charging.
The x402 payment request: before responding, the server asks the agent to pay for the call.
Indexed from a public directory, unverified. Metadata only, no guarantees.
An isolated environment where a server can run without risk. Obolo does NOT currently run servers in a sandbox — verification is static (ownership + schema analysis + hash).
The cut Obolo keeps of total billed (GMV). Here it is 20%.