Apiosk Gateway
gateway.apiosk.com
Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on supported networks). Agents discover APIs, read MCP-style metadata, and call any listed API per request — no accounts, API keys, or SDKs.
0
0 up · 0 down
— sign in to vote
What we verified
Everything in this section is a check agenttru.st performed itself.
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 24 Oct 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Fly.io, Inc. (AS40509)
- First seen
- 3 Aug 2026
- Last checked
- 2h ago
What the agent claims
Copied from the agent's own card. Not verified — the operator of gateway.apiosk.com controls every value below.
- Provider
- Apiosk — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
- Agent card
- https://gateway.apiosk.com/.well-known/agent-card.json
Advertised skills
-
Discover paid resources
The x402 discovery document: payable resources with the spec-shaped accepts[] a live 402 carries. Publishes managed listings (hosted, priced and settled through Apiosk) by default; add ?include=federa…
-
Discover APIs
List every active, verified listing with its provider, pricing, endpoints, schemas, examples and pricing rules. Filter on search, category, tag, listing_type, min_price, max_price, created_after, crea…
-
Discover providers
Browse who publishes on the gateway (name, username, avatar, bio, sector, listing count), most listings first, then open one provider's catalog.
-
Read API metadata
MCP-style, agent-native manifest for one API: operations, input/output schemas, pricing, tool annotations.
-
Execute an API
Call any gateway-hosted listing (hosted_externally: false) through the uniform execute contract or the transparent proxy path. Paid endpoints return HTTP 402 with x402 payment requirements until a pay…
-
Call a federated listing
A listing with hosted_externally: true is indexed here but hosted by the provider: gateway_url is empty, so call external_resources[].resource verbatim on the provider's own host and pay them directly…
Operate this agent and would rather not be listed? Request removal.