Skip to main content
USE CASES

Who builds with Blockchain0x.

Four use cases, three personas, one platform. Find the one that matches your work and start there.

FOUR USE CASE PATTERNS

Pick the closest match and dive in.

Each page goes deep on the persona's typical day, the right Blockchain0x plan for that shape of work, and a concrete walk-through of how to start.

PERSONA 1

AI agent builders

You built an agent that does useful work. You want it to look credible and accept payment without assembling a custom crypto stack.

TYPICAL PROFILE
  • -Solo developer or 2-3 person team
  • -1-3 agents in production
  • -Built on LangChain, CrewAI, or OpenAI Agents SDK
  • -Wants a public page that ranks
Read the deep-dive
PERSONA 2

MCP server operators

You run an MCP server. AI clients invoke your tools thousands of times a day. You want them to pay per call, in USDC, without manual API keys.

TYPICAL PROFILE
  • -MCP server in production (Claude Desktop, Cursor, Cline clients)
  • -Per-call pricing economics
  • -Wants x402-compatible flow
  • -Needs audit logs for usage
Read the deep-dive
PERSONA 2 VARIANT

API providers

You sell an API. AI agents cannot fill out credit card forms. You want them to pay programmatically via 402 Payment Required.

TYPICAL PROFILE
  • -Existing API with developer customers
  • -Looking to add agent-friendly billing
  • -Comfortable with x402 protocol
  • -Wants per-call USDC billing alongside Stripe for humans
Read the deep-dive
PERSONA 3

Web3 automation teams

You run many bots for many clients. Each needs its own wallet, its own limits, its own audit trail, and per-agent visibility for the client.

TYPICAL PROFILE
  • -Agency or in-house ops team
  • -5+ concurrent agents
  • -Compliance or reporting obligations
  • -Needs team-seat sharing per client
Read the deep-dive
HOW THE PERSONAS MAP TO PRODUCT SURFACES

Same product, different parts in the spotlight.

Every use case uses every Blockchain0x surface eventually. What differs is which surfaces dominate the daily workflow. This is the lens that tells you which plan tier and which integrations to prioritize.

Use caseWalletAPIIdentitySpend
AI agent buildersCriticalSecondaryCriticalUseful
MCP server operatorsUsefulCriticalSecondaryUseful
API providersUsefulCriticalSecondaryCritical
Web3 automation teamsCriticalCriticalUsefulCritical

Read the matrix top-to-bottom: AI agent builders care most about the public-facing wallet and identity (their agent's "storefront"); MCP server operators and API providers care most about the API and spend policy (their agent's "checkout"); Web3 automation teams care about all four because they are running production-grade ops across many agents.

For pricing: AI agent builders typically start on Free, upgrade one agent to Pro when revenue starts. MCP operators and API providers usually go straight to Pro because the API and webhooks are required from day one. Web3 automation teams move to Business once they have a handful of clients, for the audit logs and team seats.

WHICH ONE ARE YOU

A four-question decision tree.

Answer top to bottom. The first "yes" lands you on the right deep-dive page. If you make it through all four with "no", you do not fit a current persona; reach out and we will help.

  1. Q1

    Are you building ONE agent that you yourself operate?

    YES →AI agent builders. Solo-builder pricing and ergonomics fit.

    NO: continue to Q2.

  2. Q2

    Are you running an MCP server that AI clients call?

    YES →MCP server operators. Our middleware turns paid tools into x402 endpoints.

    NO: continue to Q3.

  3. Q3

    Is your product an HTTP API used by AI agents?

    YES →API providers. Wrap your API with our 402 decorator and bill in USDC.

    NO: continue to Q4.

  4. Q4

    Are you operating many agents for clients or strategies?

    YES →Web3 automation teams. Per-agent wallets, team-seat sharing, audit logs across many agents.

    NO: reach out at [email protected] - your use case may need its own page.

Two-yes answers are common (an MCP server operator who is also building their own agent on top of it, an agency that runs an API). Pick whichever yes maps to your primary daily workflow; the other use cases will still be useful as supporting reading.

FREQUENTLY ASKED

Four use-case questions.

What if I fit two of these personas?

Many users do. A solo agent builder who also runs an MCP server is both Persona 1 and Persona 2. The right move is to start from whichever description matches your nearest-term work and skim the other one for the patterns that overlap. Pricing, API access, and product surface are identical across personas; we segment the marketing pages to make starting points easier to find, not because the underlying product is different.

I do not fit any of these. Should I still use Blockchain0x?

Yes, if you have an AI agent (broadly defined) that you want to receive or send USDC payments programmatically. The four personas are the most common patterns we see, not an exhaustive list. If your use case is genuinely new (a research agent that pays human reviewers, an LLM judging contests that pay winners, a DAO-coordinated agent collective), email [email protected] and we will write you onto the page if it generalizes.

How are the four use cases different in terms of pricing or features?

They are not, at the platform level. All four use cases get access to the same four product surfaces (Agent wallets, Payment API, Agent identity, Spending controls) and the same three plans (Free, Pro, Business). Differences show up in which surfaces matter most: agent builders lean on the public page and identity; MCP operators lean on the API and x402; API providers lean on webhooks; automation teams lean on Business-tier audit logs and team seats. Pick a plan based on volume and feature need, not based on persona.

Can the use cases mix in a single workspace?

Absolutely. A common workspace shape is: 2-3 agent-builder agents on Free for experiments, 1 MCP server agent on Pro, 1 API-provider agent on Business. All four flavors coexist under one Stripe customer with one consolidated invoice. Workspace seats and audit logs roll up across all of them. The per-agent pricing model is exactly what makes this work; you are not paying for capability across the whole workspace, only for the agents that have grown beyond Free.

Find your shape, then start.

Every use case lands at the same signup flow. Free to start. Five minutes to your first agent wallet.