Arysphere

For agents

If you are an agent, this is the whole integration: one GET, one 402, one payment, one retry. No signup, no key management, no subscription state to track.

The call flow

  1. GET the endpoint. Every route is a GET with query parameters, for example a token verdict with ?token=<contract> or a transaction decode with ?hash=<tx-hash>.
  2. Read the 402. An unpaid call returns HTTP 402 with PAYMENT-REQUIRED carrying the x402 v2 terms: asset (USDC), networks, payee and the fixed price. Where the MPP rail is up, the same 402 also offers it via WWW-Authenticate: Payment.
  3. Pay and retry. Pay the stated amount in USDC on Base, Polygon or Arbitrum, then retry the same GET with the PAYMENT-SIGNATURE header. The paid result returns as JSON.

A sketch, not a credential

GET https://api.arysphere.com/v1/ventures/x402_bazaar_token_verdict_v2/base_token_verdict_v3?token=<contract>
→ 402 PAYMENT-REQUIRED
  asset: USDC · networks: Base, Polygon, Arbitrum · price: $0.01

# pay, then retry with the payment signature:
GET https://api.arysphere.com/v1/ventures/x402_bazaar_token_verdict_v2/base_token_verdict_v3?token=<contract>
  PAYMENT-SIGNATURE: <your-payment-signature>
→ 200 {"ok": true, "grade": "MID", "one_liner": "…", "result": {…}}

Placeholders above are placeholders. The authoritative route paths, parameters and prices are in the OpenAPI document — read that, not this page, when you build.

What you get back

Costs, bounded by construction

Every price is fixed per endpoint and stated before you pay: $0.01 for verdicts, $0.005–$0.006 for bundles and the Base transaction decoder, $0.002–$0.003 for individual reads. There is no subscription and no minimum, so an agent's spend is exactly its calls.

Where to start