← Liquid State
For AI Agents & Autonomous Systems

The crypto intelligence layer, built for machines to read and pay.

Pay-per-call market data over x402, a first-party MCP server, machine-readable manifests, a free signal API, and a legacy paper-strategy record with stated limitations — one programmable surface for the autonomous economy. Information, not financial advice.

agent — x402 settlement handshake
$ curl https://www.liquidstate.tech/api/x402/farside-btc-etf
← HTTP/1.1 402 Payment Required   PAYMENT-REQUIRED
  accepts[0]: { scheme: "exact", network: "eip155:8453", amount: "10000" }

$ curl -H "PAYMENT-SIGNATURE: <signed-usdc-authorization>" …/api/x402/farside-btc-etf
← HTTP/1.1 200 OK   PAYMENT-RESPONSE: <settle proof>
  { "leg_id": "…", "receipt_hash": "…" }

Discovery: /.well-known/x402 · /desk-tape-agents.md · /.well-known/agent-offer.json · /openapi.json · /api/mcp

Desk tape

Discover, pay, cite, poll, verify.

  1. Discover /.well-known/x402. The Feed and the three exclusives are x402 v2 on eip155:8453 with extensions.bazaar.
  2. Pay the unpaid GET. The 402 carries PAYMENT-REQUIRED. Retry with PAYMENT-SIGNATURE. Settle proof is PAYMENT-RESPONSE.
  3. Cite leg_id from the paid Decision Leg.
  4. Poll GET /api/agents/invalidations?since=.
  5. Verify receipt_hash at GET /api/agents/receipts?leg_id=.
  6. Reserve book: GET /api/agents/desk-book. Reserve is $149. Feed $25 does not open it.

Invalidations, receipts, and the book are not catalog rows. Humans stay at /community. Builder note: /desk-tape-agents.md.

Built for the AI race

New models ship weekly. So does the infrastructure they run on.

Liquid State is designed to be consumed by autonomous systems first — every capability is discoverable, priced in the open, and machine-payable. As agent frameworks, payment rails, and model context standards evolve, the platform tracks them additively, so an agent that integrates once keeps getting more surface over time.

FAQ

Can an AI agent pay for Liquid State data autonomously?
Yes. Selected premium reads use x402 (HTTP 402) on Base mainnet (eip155:8453): the endpoint returns a 402 quoting the exact price in USDC, and the agent retries with a PAYMENT-SIGNATURE header. A settled response sets PAYMENT-RESPONSE. No account, no API key, no human in the loop.
How does an agent discover what Liquid State offers?
Three machine-readable entry points: /.well-known/x402 lists the payable resource catalog, /llms.txt maps the platform for language models, and /openapi.json describes every public endpoint in OpenAPI 3.1. A first-party MCP server at /api/mcp exposes the read tools directly.
How does an agent follow a Decision Leg?
Discover /.well-known/x402, pay the exclusive, cite leg_id, poll GET /api/agents/invalidations?since=, verify receipt_hash at GET /api/agents/receipts?leg_id=, and read the Reserve book at GET /api/agents/desk-book. Invalidations, receipts, and the book are not catalog rows. Humans join at /community. Feed is $25. Reserve is $149.
Is there a free tier for developers and bots?
Yes. The public Signal API returns aggregated market-regime signals as JSON with no API key, rate-limited only as a soft abuse deterrent. It is free for non-commercial use; attribution is appreciated but not enforced.
What if an agent or product needs more than the free tier?
Join The Feed — $25 or The Reserve — $149. x402 pay-per-call, the free Signal API, and MCP stay available — they are not a third membership SKU.
Is any of this financial advice?
No. Everything Liquid State publishes is information, not financial advice. There are no guaranteed-return claims and no fabricated figures; a compliance gate rejects prescriptive buy/sell calls before publication.

Information, not financial advice. Not a recommendation to trade.