Hosted facilitator
Access402 verifies and settles supported x402 v2 payments. Your WordPress server never receives Coinbase facilitator credentials.
Adapters / WordPress
Native WordPress adapter
Native WordPress adapterx402 payments for WordPress—without rebuilding your site.
WordPress was the first native adapter for the Access402 platform. Protect selected posts, pages, Media Library files, and existing REST API routes while Access402 handles the hosted x402 verification and settlement flow.
No custom payment code Hosted facilitator included
Turnkey, with clear boundaries
The plugin stays in WordPress. The payment infrastructure is managed for you.
Access402 removes the need to build an x402 verifier, settlement service, wallet dashboard, or payment activity system around your WordPress site.
Guided wallet setup
Access402 creates the Coinbase project wallet and assigns it automatically, so you never paste a receiving address into WordPress.
Direct USDC settlement
Live payments settle to the project wallet in USDC on Base. Access402 does not custody the funds or run payout schedules.
Activity and usage
Review payment outcomes, access events, wallet balances, transaction details, and monthly plan usage in one dashboard.
Posts & pages Media files REST API routes Role permissions
Built for site owners
Your writers keep publishing. Access402 handles the x402 paywall.
You do not need to turn your editorial team into payment engineers. Authors create posts and pages as usual. An administrator chooses which specific content should require payment, names the resource, sets a USDC price, chooses the access policy, and turns the rule on.
Human-facing pages can stay public while high-value research, structured data, Media Library files, or agent-facing routes become a new revenue stream. Allowed WordPress roles can bypass the payment requirement so your own team can keep reviewing content normally.
- Keep your theme, SEO URLs, authors, and publishing process
- Set a different price for each protected resource
- Route settlement to the wallet assigned to your Access402 project
What is x402?
HTTP-native payments that software can complete.
x402 is a payment protocol built around the HTTP 402 Payment Required status. A protected WordPress resource describes the price, network, receiving wallet, and payment instructions in a machine-readable challenge.
An AI agent or API client signs the payment authorization and retries the request. Access402 verifies and settles the USDC payment, then WordPress returns the original page, file, or API response. Browser visitors use the same challenge through a MetaMask checkout.
Three simple steps
From WordPress post to payable x402 resource.
The adapter lives inside the WordPress admin you already know.
01
Connect WordPress to your Access402 project
Create a WordPress installation in the Access402 dashboard, paste its installation ID and API key into WordPress, then test the connection. Keep the same credential and use the Sandbox/Live toggle to choose Base Sepolia testing or real USDC payments on Base.
02
Choose the content and set the price
Search for a post, page, or Media Library file—or enter an existing REST API route exactly. Set its USDC price, then choose payment for every request, a reusable grant after one payment, or time-limited access.
03
Let agents pay and unlock automatically
When an agent requests the resource, WordPress returns an x402 v2 HTTP 402 challenge. Access402 verifies and settles the signed USDC payment, records the event, and WordPress delivers the resource.
What you can monetize
Start with the content agents value most.
Protect only the resources that make sense for your business. Public pages can stay public.
Premium posts & pages
Research, analysis, archives, or subscriber-quality editorial content.
Existing REST API routes
Protect structured content, datasets, listings, or endpoints registered by another plugin.
Media Library files
Sell reports, exports, media packages, templates, and data files at their existing WordPress URLs.
Team-friendly access
Let selected WordPress roles bypass payment while agents still pay.
What happens on every request
A machine-native payment flow, hidden behind a simple rule.
Agent requests content
WordPress matches the request to an enabled protection rule.
WordPress returns HTTP 402
The x402 v2 challenge includes the USDC amount, Base network, receiving wallet, resource, and payment instructions.
Access402 verifies payment
The signed authorization is verified and settled against the installation's project and receiving wallet.
WordPress unlocks the response
The paid post, page, Media Library file, or REST API response is delivered to the agent.
WordPress x402 FAQ
Questions from site owners.
Is Access402 only for WordPress?
No. Access402 is a managed x402 platform for websites and APIs. WordPress was its first native adapter, and FastAPI is also available for Python APIs.
Do I need to replace my WordPress theme or hosting?
No. Access402 works through a WordPress plugin. Your theme, authors, URLs, and publishing workflow stay in place. Before protecting Media Library files in production, run the included server routing check and review any CDN or media-offload configuration.
What can I protect with x402?
The adapter supports individual WordPress posts and pages, media files, and WordPress REST API routes. Search for WordPress resources by title or filename, or enter a REST route directly. MIME types are detected automatically.
Do I need to write code?
No custom payment code is required. Install the plugin, create an Access402 project and WordPress installation, paste its installation ID and API key, then choose resources and prices in WordPress.
Does Access402 operate the x402 facilitator?
Yes. Access402 runs the hosted verification and settlement service. The WordPress site authenticates with its scoped installation key; customers do not configure or expose Coinbase facilitator credentials.
Do I need to create and manage my own crypto wallet?
No. Access402 creates a dedicated Coinbase CDP wallet for the project and automatically uses it as the payment destination. You do not paste a wallet address, private key, or seed phrase into WordPress.
Can payouts go directly to my bank account?
Not directly through Access402 yet. Live payments settle to the Coinbase wallet Access402 created for the project, and you can access and manage the funds through Coinbase. Integrated Access402 cash offboarding is planned for a later release.
Can AI agents discover and buy my WordPress content automatically?
Yes. A WordPress rule can advertise x402 v2 discovery metadata to CDP Bazaar, including the method and optional input/output schemas for REST routes. CDP validates the public endpoint and indexes it after its first successful CDP settlement. Discovery can be removed without disabling payment protection.
What can I monitor in the dashboard?
The dashboard shows the WordPress installation, synchronized rules, receiving wallet and balance, payment and access activity, transaction details, and monthly plan usage.
Can I test it before charging agents?
Yes. Keep the same installation ID and API key, then use the WordPress Sandbox/Live toggle to switch between test USDC on Base Sepolia and real USDC payments on Base.
Will normal readers see a crypto checkout?
Only when they open a protected resource. Browser visitors receive a MetaMask checkout, while x402-compatible agents and API clients receive the machine-readable HTTP 402 challenge. Selected WordPress roles can bypass payment.
Does Access402 create a REST API for me?
No. Access402 adds payment protection to an existing WordPress REST API route, including endpoints registered by your theme or another plugin. Enter the exact route you want to protect.
How are protected media files stored?
Access402 preserves the WordPress attachment record, metadata, and original URL while moving the public file bytes into private storage. WordPress streams the file after payment, and disabling the final rule restores the public files.