How it runs on Pocket

Akashi is one registered Pocket Network service. A paid run travels as a real Pocket relay, from Akashi's staked application to Akashi's supplier, and the claims and proofs settle on Pocket Beta.

One service

Akashi is a single Pocket Network service, tool-router ("Akashi Tool Router"), registered on Pocket Beta. Every tool in the catalog is a path on that one service, so adding a tool needs no new on-chain registration.

Record	Value
Service id	`tool-router`
Network	Pocket Beta
Compute units per relay	20,000
Registration	tx `A96AAAB2…AFE67F7`, height 711952
Service owner	`pokt16p53au7ctwrtfdwd23pt2tv54nj9f0n8wsj805`
Supplier operator	`pokt1qnrjr3susgpyh4a4rx8f0x0wd6pqdtptr50ayg`
Application stake	tx `113EFC51…6BCC0E1E8E0CF5DE85835BBC`
Supplier stake	tx `E8997D51…5AD4762ABD02F60645634784B97D4915`, 60,000 POKT, endpoint `https://relay.useakashi.xyz` (REST)
First relay claim	tx `AC215AB4…E489F17594371D64988A89F3F9A3E244`, proof `6729C253…517067F2C09BF945D7659A4703E06560`, settled 2026-10-07
Service Audit	A1 to A9 all `PASS` (run it live)

The path of a paid run

Gateway. Your request reaches the public gateway at https://api.useakashi.xyz. Without a payment it answers 402. With one, it verifies the x402 signature.

Pocket relay. The gateway forwards the run through pocket-ap, which signs it with Akashi's staked application. It travels as a real Pocket relay.

Supplier. Akashi's supplier, a RelayMiner, receives the relay and passes it to the tool-router backend.

Backend. The backend validates the input against the tool's schema, calls the upstream tool within the run deadline, trims oversized output and returns the run envelope.

Settlement. The answer travels back the same way. On a 2xx, the gateway settles your USDC payment on Base Sepolia. On Pocket, the supplier's claims and proofs for the relays settle on Pocket Beta.

agent ──x402──▶ gateway ──relay (pocket-ap, Akashi's application)──▶ RelayMiner (Akashi's supplier) ──▶ tool-router backend ──▶ upstream tool

Two payments are involved, and they are separate. You pay Akashi per run in USDC over x402. Akashi's application pays for the relay on Pocket Network.

Free reads do not use a relay

discover, inspect, GET /v1/catalog and GET /v1/endpoints/{provider}/{endpoint} are answered by the backend directly through the gateway. They are free, so there is nothing to relay or settle.

The direct fallback

If the relay hop is down (pocket-ap unreachable, no session, or the supplier not answering), the gateway calls the backend directly instead of failing the run. It never presents that as a relay. Every run response says which way it went in the X-Akashi-Via header:

`X-Akashi-Via`	Meaning
`pocket`	The run went through a Pocket relay to Akashi's supplier
`direct`	The gateway called the backend directly

The CLI shows the same value as receipt.via. GET /v1/version reports how the gateway is configured: "relay": "pocket" or "relay": "direct".

Limits the relay sets

Pocket gateways expect an answer in about 10 seconds and cap request bodies near 64 KiB. Akashi stays inside both: request bodies are limited to 64 KiB, every run finishes in under 9 seconds (each tool has its own deadline), and output is trimmed near 60 KB. See Limits.

Pocket's tools, and what each did

Tool	What it did for Akashi
Pocket Service Builder (skill and MCP server at `mcp.pocketmcp.network`)	Checked that `tool-router` was free on both networks, read the live fees, minimum stakes and compute-unit price, validated the service card, watched sessions and claims, and runs the Service Audit.
`pocketd`	Registered the service, staked the supplier for it, and staked the application that signs Akashi's relays.
HA RelayMiner (relayer, miner and Redis)	Akashi's own supplier. The relayer checks each signed relay and forwards it to the `tool-router` backend; the miner builds the session trees and submits the claims and proofs.
`pocket-ap`	Signs every paid run as a relay from Akashi's staked application, so the gateway never holds a Pocket key.
Service card (`pocket-service-card/v1`)	The on-chain description gateways read: what the service does, its REST transport, an identity probe (`GET /v1/version` must name `tool-router`), functional probes, and the OpenAPI spec.
Pocket Explorer	The public record of the service, its stakes and its claims.

Two things worth knowing if you run a supplier

Settled claims are paid from the application's stake. An application staked at exactly the minimum (1,000 POKT on Beta) drops below it with its first settled relay, and the network unstakes it. Akashi's application is staked with headroom (1,150 POKT, about 187,000 relays at 800 uPOKT).
Name the RelayMiner's Redis uniquely. On a host where several Docker Compose stacks share one network, a service called redis can resolve to another stack's Redis. Akashi's is pocket-relay-redis.