Back to Browse
Pocket Network – Fraxtal JSON-RPC
x402
Pocket Network – Fraxtal JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).
Provides read-only Ethereum-compatible JSON-RPC access to the Fraxtal OP-Stack L2 blockchain, served by Pocket Network's decentralised node fleet, billed per-request in USDC.
Price / call$0.005
Success—
StatusUnknown
How this service works
Read-only JSON-RPC access to Fraxtal, the OP-Stack L2 by Frax, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.
Output
A standard Ethereum JSON-RPC response object containing a 'result' field with the requested on-chain data (balance in wei, block object, transaction receipt, encoded return value, etc.) or an 'error' object if the call failed. Responses reflect the current state of the Fraxtal OP-Stack L2 chain as seen by Pocket Network's decentralised supplier set.
Example use cases
DeFi portfolio balance check
“Can you fetch the token balance of address 0xDeF…5678 on Fraxtal mainnet so I can see how much FRAX they're holding?”
Smart contract state inspection
“Call the totalSupply view function on the Fraxtal contract at 0x123…abc — I need to know the current circulating supply of that token.”
Transaction confirmation monitoring
“Look up the receipt for transaction 0xabc…def on Fraxtal and tell me whether it succeeded and how much gas was used.”
Technical details
Endpoint
POSThttps://agent.pocket.network/v1/fraxtal?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need trustless, decentralised, pay-per-use read access to the Fraxtal OP-Stack L2 without managing API keys or subscriptions. It is ideal for agents that make sporadic or unpredictable call volumes to Fraxtal and want to pay only for what they use in USDC. Prefer it over centralised RPC providers when decentralisation and censorship-resistance of the node layer matter, or when no account sign-up is acceptable.
Side effects
- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Write methods (eth_sendRawTransaction) are not supported — returns error or is rejected
- Malformed params array returns error code -32602 (invalid params)
- Payment failure (insufficient USDC balance) results in HTTP 402 before the RPC call is made
- Node temporarily out of sync may return stale block data
- Rate or per-request payment processing delays can cause timeouts
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| method | string | JSON-RPC read method, e.g. eth_getBalance |
| params | — | Parameters per the Ethereum JSON-RPC spec |
Output
Schema · Response
{
"type": "json",
"example": {
"data": {
"id": 1,
"result": false,
"jsonrpc": "2.0"
},
"portal": {
"serviceId": "fraxtal",
"provenance": "third-party-supplier",
"schemaCheck": "passed"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"