Fishy Island just got easier to explore.
Spectate Mode is now available, allowing new players to preview the map before fully entering the game with the initial 10,000 $FISHY.
This helps players understand the world, check the vibe, and get comfortable before making their first cast.
Welcome to the island and happy fishing!
Start Fishing: https://t.co/wl2YhunAhe
API publishing on Rail402 starts with trust.
Before publishing, builders can complete their profile by connecting X and GitHub, helping users and agents verify credibility, ownership, and service integrity before interacting with any listed API.
Once verified, providers can publish machine-readable services, configure endpoints, define schemas, set pricing, and enable autonomous systems with x402-powered access on @base.
Rail402 is building the infrastructure for APIs to become programmable economic endpoints — discoverable, payable, and verifiable by agents and applications.
Next: automating Rail402 through our MCP, with integrations for Claude, OpenAI, Cursor, and more.
$RAIL is now live on Base via @clanker_world
Rail402 is building the transaction layer for autonomous systems, enabling machines to discover services, settle access, and coordinate economically through programmable infrastructure powered by x402.
Contract Address: 0xd172c36baff91269ecc09fc62e831a696979db07
https://t.co/HkCOyub6Mp
How Rail402 lets autonomous agents pay for APIs on @base — a breakdown.
An agent acting on its own needs three things humans take for granted: a way to pay, a way to prove who it is, and a way to credit who built what. Rail402 composes three Base-native standards to provide all three. Here is how they fit together.
x402 — Payments. When an agent calls a paid endpoint, the server replies with HTTP 402 Payment Required, encoding the amount, the recipient address, and the network directly in the response. The agent settles in USDC on Base — roughly two-second finality — and retries the request carrying the transaction hash as proof. Rail402 verifies that transfer against on-chain state before any data is returned. No API key, no account, no subscription. The payment is the authentication.
ERC-8004 — Identity. Payment answers "did they pay." Identity answers "who is calling." ERC-8004 is an on-chain registry for agent reputation and capabilities. Rail402 is designed to read it so providers can price and gate access by the caller's standing — trusted agents earn better terms, unknown ones get stricter limits. The credential is the agent's on-chain history, not a secret it has to store.ERC-8021 — Attribution. In a multi-agent pipeline, one call triggers another, which triggers another.
ERC-8021 builder codes attach revenue attribution to each step, so when value flows through a chain of delegated calls, the provider that originated the work still gets credited. Composable revenue, settled on-chain.
Together, these are the three primitives an autonomous economy runs on: x402 moves the value, ERC-8004 establishes trust, ERC-8021 routes the credit. Software transacting with software — discoverably, verifiably, with no human in the loop.
The payment layer is live on Base mainnet. The SDK, discovery spec, and MCP server are open source at https://t.co/inoSczUCkP.