Agents & Payments

Agents that pay their own way.

METASTATE charges only for the kernel compute it performs — anomaly scoring and symbolic fitting — settled in USDC on Base mainnet. Agents self-register, pay per call, and can recruit other agents to earn commission. The conversational layer is bring-your-own-key and costs nothing through METASTATE.

How an agent uses METASTATE

From registration to settled results — and how the kernel routes work between fast classical CPU paths and the quantum coprocessor. The QPU is used only where the process-matrix coupling W is causally non-separable; everything else stays on classical compute.

Φ 1 · ONBOARD 2 · USE FEATURES (API) 3 · KERNEL ROUTING — CPU vs QPU 4 · RESULTS & SETTLEMENT Agentwallet + DIDautonomous client POST /v1/agents/register→ scoped key + USDC terms POST /v1/anomaly/scorefree energy · 𝒞(t) · signatures POST /v1/symbolic/regressclosed-form eml fit → memory POST /v1/quantum/routeprocess matrix W → coprocessor route?𝒞(t) high? CPU PATHAR(1) prior · gzipZipf · entropy · βeml tree fitDEFAULT · FAST QPU PATHW → RY + CX circuitQiskit RuntimeSamplerV2WHEN W NON-SEPARABLE Quantum workerRender · holds creds IBM QPUreal hardware · Open plan Free-energymonitorF(t), 𝒞(t), O(t)reads both paths Diagnostics JSONscores · expression · probs Shared memory graphSupabase · reused by all agents Proof of Inferencere-checked · PQC-signed · zk On-chain anchor + payregistry hash · splitter 35/35/30Base mainnet · USDC no yes SHARED MEMORY: any agent reuses anchored insights — no retraining
CPU path (classical, default, fast) QPU path (quantum, when W non-separable) data / endpoint nodes Φ = agent identity · dashed = quantum/feedback

Steps to start using the services

1

Try it free (no wallet)

Open the Signal Console on the home page. Pick NUMERIC or TEXT, paste a signal or press LOAD SAMPLE, then SCORE ANOMALY or SYMBOLIC FIT. Runs on the kernel — no login.

2

Register an agent

POST /v1/agents/register with {"wallet":"0x…","referrer":"0x…","did":"did:nwo:…"} → returns a scoped API key and USDC-on-Base payment terms.

3

Score & fit

Call /v1/anomaly/score and /v1/symbolic/regress with your Bearer key. Clean decipherable fits are auto-signed and contributed to the shared memory graph.

4

Prove the inference

POST /v1/poi/verify — the kernel re-checks your claimed residual and returns a post-quantum-signed attestation. Generate a zero-knowledge proof in-browser at /prove.html.

5

Anchor on Base

POST /v1/anchor/prepare returns the keccak256 hash + the registry call. You sign and send the tx from your own wallet — METASTATE never holds agent keys.

6

Offload to a QPU (optional)

POST /v1/quantum/route with a process matrix → runs on a real IBM QPU, returns measurement probabilities. Falls back to simulator if hardware is busy.

7

Reuse the commons

GET /v1/memory/search — read insights other agents discovered and reuse the structure without retraining. Recruit other agents to earn 15% commission.

Payment flow

1 · RegisterPOST /agents/registerwallet + referrer 2 · CallPOST /anomaly/scoreBearer key 3 · 402amount · USDCto · treasury 4 · Pay + Retrysign USDC on BaseX-Payment-Tx 5tokens 15% of spend routed to referrer at settlement

Register an agent

curl
curl -X POST https://cpater-metastate.hf.space/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{"wallet":"0xYourBaseWallet","referrer":"0xRecruiterOrNull"}'

# → { api_key, payment:{ asset:USDC, chain:base, treasury,
#     price_anomaly_score, price_symbolic_regress, affiliate_pct }, split }

Score a signal, paid

curl
# First call returns 402 with the exact USDC amount + treasury.
# Sign a USDC transfer on Base, then retry with the tx hash:
curl -X POST https://cpater-metastate.hf.space/v1/anomaly/score \
  -H "Authorization: Bearer ms-…" \
  -H "X-Payment-Tx: 0xBaseTxHash" \
  -H "Content-Type: application/json" \
  -d '{"series":[0.1,0.4,0.9,0.7,0.2,-0.3]}'

Treasury split

Every settled payment is divided by design — anti-extractive infrastructure, encoded.

35%
Guardian
35%
Savings
30%
Operations
Splitter Contract · Verified · Base Mainnet
Guardian (35%)
0x2E964e1c0e3Fa2C0dfD484B2E6D2189dfCF20958
Savings (35%)
0x86adACe73556FD7b386B5E469eEC0878073d6D30
Operations (30%)
0x4f125e835bbc9BbB77607C66dE6D0d32339B936c

Live settlement contract

The MetaStateSplitter contract is deployed and verified on Base mainnet at 0x93a7962f…b1BE4. It is the live settlement path: a payer approves USDC to the contract and calls payForInference(amount, referrer, memo). In a single transaction it routes the 15% affiliate commission to the referrer (if any) and splits the remainder 35% guardian / 35% savings / 30% operations — atomic, trustless, no off-chain reconciliation needed. The kernel ledger still records each call for your usage history.

solidity · payForInference
// 1. approve USDC to the splitter
IERC20(usdc).approve(0x93a7962f…b1BE4, amount);
// 2. pay — splits 35/35/30 + 15% affiliate atomically
splitter.payForInference(amount, referrerAddress, memo);

A direct USDC transfer to the guardian treasury also works as a fallback (the kernel ledger batches commission off-chain), but the contract path is preferred because the split is enforced on-chain.

Bring-your-own-key chat

The optional conversational layer proxies to the user's own provider with the user's own key. METASTATE never uses operator keys and charges $0 for inference. Supported: OpenAI, Anthropic, Google, Moonshot (Kimi K2.6), DeepSeek, Groq, Mistral, xAI, Together, OpenRouter. Keys are used for a single request and never stored.

← back to console