x402 CLI

The terminal gateway for x402-powered APIs on @base.

Exploring HTTP 402 payments, USDC API access, and agent-ready workflows.

[x402 CLI @x402cli]

Support x402 CLI by holding $X402CLI.

x402 CLI is being built as an experimental discovery and testing layer for x402-powered APIs on Base — focused on HTTP 402 inspection, registry metadata, MCP-ready workflows, Builder Code attribution research, and future agent-ready API infrastructure.

Holding $X402CLI means supporting the long-term development of the x402 CLI ecosystem as we continue building in public.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA (Just updated by adding Token Address)

[x402 CLI @x402cli]

$X402CLI is now launched on Base via @bankrbot

CA : 0x6fBEb18fc6Ab14b170EcfB21c9a2f2384b155bA3
https://t.co/2kILXJuC9h

Website : https://t.co/DHGhXILOgi
Github Repository : https://t.co/SnRrywsmqj

[x402 CLI @x402cli]

Staking is being planned for x402 CLI.

The next direction is to introduce staking support for $X402CLI, $USDC, and $BNKR inside https://t.co/b24c8WATXa as part of the ecosystem utility layer.

$X402CLI CA : 0x6fbeb18fc6ab14b170ecfb21c9a2f2384b155ba3 (Base)

The idea is simple: give supporters and ecosystem participants a way to stay aligned with the long-term development of x402 CLI while we continue building around x402-powered APIs on Base, registry metadata, HTTP 402 inspection, MCP-ready workflows, and Builder Code attribution research.

This is still in the planning stage.

More details will be shared as the staking model, mechanics, and integration direction become clearer.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/0LcokrGMpE…

[x402 CLI @x402cli]

Support x402 CLI by holding $X402CLI.

x402 CLI is being built as an experimental discovery and testing layer for x402-powered APIs on Base — focused on HTTP 402 inspection, registry metadata, MCP-ready workflows, Builder Code attribution research, and future agent-ready API infrastructure.

Holding $X402CLI means supporting the long-term development of the x402 CLI ecosystem as we continue building in public.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA (Just updated by adding Token Address)

[x402 CLI @x402cli]

x402 CLI v0.3 is here.

This update introduces the Registry Metadata Layer — a more structured way to document x402-powered APIs on Base.

Instead of only showing demo listings, each API can now be described with metadata around endpoint, network, asset, price, payment protocol, MCP-ready status, Builder Code attribution research, and example HTTP 402 responses.

What’s new:
→ public registry JSON
→ API detail pages
→ metadata schema previews
→ curl examples
→ HTTP 402 response examples
→ expanded registry fields for MCP-ready workflows and Builder Code research

Still early and experimental. No real payment execution yet.

The goal is to make x402 APIs easier to discover, inspect, document, and prepare for future agent workflows.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

Back in the editor for x402 CLI.

The next update is focused on making the project feel more like a real discovery layer: registry metadata, API detail pages, Builder Code fields, MCP-ready workflow notes, and better documentation.

Still early, still building.

https://t.co/b24c8WATXa

[x402 CLI @x402cli]

Back in the editor for x402 CLI.

The next update is focused on making the project feel more like a real discovery layer: registry metadata, API detail pages, Builder Code fields, MCP-ready workflow notes, and better documentation.

Still early, still building.

https://t.co/b24c8WATXa

[x402 CLI @x402cli]

Building x402 CLI on @base 📚🟦

A terminal-inspired discovery layer for x402-powered APIs on Base.

HTTP 402 inspection, API registry exploration, Base + USDC flows, and future MCP-ready agent workflows.

Website : https://t.co/b24c8WATXa

#BuildOnBase #Crypto #Web3 #Base #Agents #AI #x402cli

[x402 CLI @x402cli]

What’s next for x402 CLI:

We’re moving toward a Registry Metadata Layer.

Each x402-powered API should be more than just a listing. It should have clear metadata around endpoint, price, network, asset, payment protocol, MCP-readiness, Builder Code attribution research, and example HTTP 402 responses.

The goal is to make x402 APIs easier to discover, inspect, document, and prepare for future agent workflows.

Next: registry JSON, API detail pages, metadata schema, curl examples, and HTTP 402 response examples.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

New update for x402 CLI.

We’re adding Builder Codes / ERC-8021 attribution research into the project direction.

As x402 grows, payment execution is only one part of the stack. The next important layer is attribution: understanding which apps, APIs, builders, and agent workflows are actually driving x402 traffic on Base.

x402 CLI is now tracking this as part of its registry metadata model.

This means future API listings can include more than just endpoint, price, network, asset, and MCP-readiness. They can also start describing attribution fields such as Builder Code status, app-level attribution, service attribution, and related x402 traffic metadata.

Current focus:

HTTP 402 payment inspection
x402 API registry metadata
Base + USDC flow exploration
MCP-ready agent workflow research
Builder Codes / ERC-8021 attribution research

This is still research/planned, not live settlement integration yet.

The goal is to make x402 APIs easier to discover, understand, document, and eventually attribute across real app and agent usage.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

$X402CLI is now launched on Base via @bankrbot

CA : 0x6fBEb18fc6Ab14b170EcfB21c9a2f2384b155bA3
https://t.co/2kILXJuC9h

Website : https://t.co/DHGhXILOgi
Github Repository : https://t.co/SnRrywsmqj

[x402 CLI @x402cli]

https://t.co/6ZiJ1MRlYX

[x402 CLI @x402cli]

New update for x402 CLI.

We’re adding Builder Codes / ERC-8021 attribution research into the project direction.

As x402 grows, payment execution is only one part of the stack. The next important layer is attribution: understanding which apps, APIs, builders, and agent workflows are actually driving x402 traffic on Base.

x402 CLI is now tracking this as part of its registry metadata model.

This means future API listings can include more than just endpoint, price, network, asset, and MCP-readiness. They can also start describing attribution fields such as Builder Code status, app-level attribution, service attribution, and related x402 traffic metadata.

Current focus:

HTTP 402 payment inspection
x402 API registry metadata
Base + USDC flow exploration
MCP-ready agent workflow research
Builder Codes / ERC-8021 attribution research

This is still research/planned, not live settlement integration yet.

The goal is to make x402 APIs easier to discover, understand, document, and eventually attribute across real app and agent usage.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

Building x402 CLI on @base 📚🟦

A terminal-inspired discovery layer for x402-powered APIs on Base.

HTTP 402 inspection, API registry exploration, Base + USDC flows, and future MCP-ready agent workflows.

Website : https://t.co/b24c8WATXa

#BuildOnBase #Crypto #Web3 #Base #Agents #AI #x402cli

[Base @base]

Your favorite agent just used Base

[x402 CLI @x402cli]

https://t.co/yJjPdoVHh3

[x402 CLI @x402cli]

This update adds more focus around:

→ registry schema for x402 APIs
→ MCP-ready API metadata
→ command references
→ HTTP 402 response examples
→ MPP / Tempo research notes
→ clearer roadmap and project status

https://t.co/HWpinDaYzw

See more on Repo : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

New update for x402 CLI.

We’re adding Builder Codes / ERC-8021 attribution research into the project direction.

As x402 grows, payment execution is only one part of the stack. The next important layer is attribution: understanding which apps, APIs, builders, and agent workflows are actually driving x402 traffic on Base.

x402 CLI is now tracking this as part of its registry metadata model.

This means future API listings can include more than just endpoint, price, network, asset, and MCP-readiness. They can also start describing attribution fields such as Builder Code status, app-level attribution, service attribution, and related x402 traffic metadata.

Current focus:

HTTP 402 payment inspection
x402 API registry metadata
Base + USDC flow exploration
MCP-ready agent workflow research
Builder Codes / ERC-8021 attribution research

This is still research/planned, not live settlement integration yet.

The goal is to make x402 APIs easier to discover, understand, document, and eventually attribute across real app and agent usage.

Website : https://t.co/b24c8WATXa
Github Repository : https://t.co/IgIdSFIxqA

[Base Build @buildonbase]

Integration.

Paste this prompt into any coding agent:

"Follow https://t.co/D1YJcI3evd to integrate Base Builder Codes into my x402 app."

Then view transactions in the Base Dashboard!

[x402 CLI @x402cli]

This update adds more focus around:

→ registry schema for x402 APIs
→ MCP-ready API metadata
→ command references
→ HTTP 402 response examples
→ MPP / Tempo research notes
→ clearer roadmap and project status

https://t.co/HWpinDaYzw

See more on Repo : https://t.co/IgIdSFIxqA

[x402 CLI @x402cli]

https://t.co/YHO5bCbmq0

[x402 CLI @x402cli]

Our public repo is also available.

The repository currently acts as the open documentation hub for x402 CLI, including project overview, command references, x402 flow notes, examples, roadmap, status updates, and disclaimers.

Frontend source is not published at this stage, but the docs and project direction are public.

https://t.co/IgIdSFIxqA

Website : https://t.co/b24c8WATXa

[Base Europe @Base_EUR]

Base is building the rails to make onchain payments low-cost, instant, private, and available everywhere.

[x402 CLI @x402cli]

Our public repo is also available.

The repository currently acts as the open documentation hub for x402 CLI, including project overview, command references, x402 flow notes, examples, roadmap, status updates, and disclaimers.

Frontend source is not published at this stage, but the docs and project direction are public.

https://t.co/IgIdSFIxqA

Website : https://t.co/b24c8WATXa

[wilson.base.eth @WilsonCusack]

gm! Quick video on current Base team focus and recent ecosystem wins

[x402 CLI @x402cli]

This makes x402 much easier to build around.

Attribution, analytics, and builder-level tracking are important if paid API traffic becomes a real agent economy layer on Base.

Good timing for what we’re exploring with x402 CLI.

[Base Build @buildonbase]

Builder Codes are live for x402 on Base.

With Builder Codes, teams building with x402 can:

→ Unlock app-level analytics
→ Attribute x402 traffic to your project
→ Integrate in minutes with a coding agent

Here’s how to get started ↓

[x402 CLI @x402cli]

@base https://t.co/g1tVZh3m8m

[x402 CLI @x402cli]

Building x402 CLI.

An experimental discovery and testing layer for x402-powered APIs on Base.

The first version includes a terminal-style scanner, registry preview, command docs, mock API submission flow, and a public roadmap for exploring HTTP 402 payment workflows.

https://t.co/b24c8WATXa • Early version. More soon.

[x402 CLI @x402cli]

Building x402 CLI.

An experimental discovery and testing layer for x402-powered APIs on Base.

The first version includes a terminal-style scanner, registry preview, command docs, mock API submission flow, and a public roadmap for exploring HTTP 402 payment workflows.

https://t.co/b24c8WATXa • Early version. More soon.

[Base @base]

Everything. On. Base.