6 endpoints · 2 services live
The API marketplace built for AI agents.
One marketplace. One credential. One credit balance. Your agents discover services by intent and call them through a single CLI, REST gateway or MCP server, with metering, spending limits and receipts built in.
# discover a capability by intent $ cb clankerbay search "cake recipes" NAMESPACE COMMAND PRICE INPUTS hynx-web search 2 cr <q> hynx-web page 3 cr <id> # call it — no provider-specific integration $ cb hynx-web search "cake recipes" --limit 3 { "query": "cake recipes", "results": [ { "title": "Classic Victoria sponge", "url": "https://…" }, { "title": "One-bowl chocolate cake", "url": "https://…" } ] } ✓ 2 credits · 2 from subscription · 184 ms
How it works
From intent to answer in three calls.
Providers describe their REST APIs with OpenAPI. Clankerbay turns every operation into a command your agent can find, understand and invoke, and runs every call through one gateway.
Discover
Search by what you want done (“geocode an address”) or browse namespaces. Results show inputs, price per call and access rules.
$ cb clankerbay search "geocoding"
Inspect
Every namespace publishes an OpenAPI schema. The CLI reads it to build commands, validate arguments and render help, so there is no SDK to install.
$ cb clankerbay inspect geo-lookup
Call
The gateway authenticates your agent, checks budgets, reserves credits, calls the provider with its own credentials and returns a metered receipt.
$ cb geo-lookup geocode "Dublin"
Designed for agents
Agents shouldn't juggle twenty API keys and twenty invoices.
Clankerbay gives every agent the same predictable surface: one command grammar, one bearer token, one error format and one ledger. Humans keep control with budgets, approvals and audit trails.
Read how it works →- One credential
- Issue scoped, revocable agent tokens. Providers never see them: the gateway authenticates upstream with the provider's own secret.
- Schema-driven
- Commands come straight from OpenAPI, with typed arguments, generated help and machine-readable output. Pinned schema versions stop silent breakage.
- Budgets by default
- Daily and monthly caps, per-call limits and approval thresholds per account and per token, enforced atomically at the gateway.
- Transparent metering
- Every call records the endpoint, status, latency, credits charged and whether they came from subscription or prepaid credits.
On the marketplace
Services your agents can call today
Credits
Pay once, call anything.
Buy prepaid credits that carry forward, or subscribe for a monthly allocation at a better rate. Subscription credits are always spent first, and every charge says exactly where it came from.
Example · a 50-credit call
| Balance | Before | Charged | After |
|---|---|---|---|
| Subscription | 40 | −40 | 0 |
| Prepaid | 100 | −10 | 90 |
The usage record states: 40 credits from the subscription allocation, 10 from prepaid credits.
Already have a REST API? Let agents pay to use it.
Upload your OpenAPI schema, set a price per endpoint and keep your own authentication. We handle discovery, metering, billing and monthly settlement.