AkashiDocs

Catalog, version and health

The free GET routes, the full catalog, the gateway's identity, a readiness check and the x402 resource list.

GET /v1/catalog

Every provider and tool, with input and output schemas and prices.

curl -s https://api.useakashi.xyz/v1/catalog | jq '{hash, providers: (.providers | length), tools: (.endpoints | length)}'
FieldMeaning
servicetool-router
titleAkashi Tool Router
catalogVersionThe catalog format version
networkThe payment network, eip155:84532
categories{id, label, endpointCount} for each category in use
providers{id, displayName, summary, homepage, docsUrl, categories, terms, licence, attribution, logoDomain, endpointCount, available}
endpointsOne object per tool, the same shape as inspect
hashA content hash. It changes whenever a tool is added, removed, repriced or edited.

The gateway re-reads the catalog from the backend every minute, so a new tool becomes runnable without a gateway restart.

GET /v1/version

The gateway's identity.

curl -s https://api.useakashi.xyz/v1/version
{
  "service": "tool-router",
  "gateway": "akashi-gateway",
  "catalog": "d4d99712496be86a",
  "endpoints": 70,
  "network": "eip155:84532",
  "payTo": "0x8164dabAfc824322221654ED421715FdaA66948D",
  "relay": "pocket"
}

catalog is the catalog hash and endpoints the number of runnable tools. relay is pocket when paid runs are forwarded through a Pocket relay, and direct when the gateway sends them straight to the backend.

GET /v1/health

Readiness. Answers 200 with:

{ "status": "ok" }

GET /.well-known/x402

x402 discovery: every paid resource on this gateway.

curl -s https://api.useakashi.xyz/.well-known/x402
{
  "version": 1,
  "resources": [
    "https://api.useakashi.xyz/v1/run/akashi/answer",
    "https://api.useakashi.xyz/v1/run/akashi/business-days",
    "…"
  ]
}

Each resource is a POST route. Its price is in the 402 it returns, and in the catalog.

GET /v1/endpoints/{provider}/{endpoint}

The same object as POST /v1/inspect, addressed by URL. See GET form.

On this page