- 1Pricing page
- 2Signup
- 3Billing
- 4API key
- 5Integration
FOR API PROVIDERS
Add an agent-ready, pay-per-call channel to your existing API.
Mahshar gives providers an additional way to offer an existing API for discoverable, pay-per-call USDC access. Builders and autonomous agents get a clear interface for finding and purchasing calls; you keep operating the upstream service.
PUBLIC REFERENCES
Public product references, in one place.
Find Mahshar’s network, source, documentation, and support.Mahshar uses Circle technologies and operates on Arc Mainnet. It is not operated by, endorsed by, or part of Circle.
AN ADDITIONAL CHANNEL
Your API does not need a new business model.
Mahshar can sit alongside the way you already sell and operate your service. It does not replace or modify your existing direct customer integrations, subscriptions, domain, infrastructure, or authentication.
For a Mahshar listing, you define a supported request contract and listed base price. Mahshar adds a distinct agent and pay-per-call path through its Marketplace architecture.
TWO CUSTOMER JOURNEYS
Traditional access and agent-ready access solve different needs.
A human-led commercial journey can support ongoing relationships and negotiated plans. A machine-led journey needs terms it can inspect and act on inside a request flow.
- 1Discover
- 2Inspect price
- 3Payment requirement
- 4Pay
- 5Call
- 6Receive
WHY AGENTS CHANGE DISTRIBUTION
Being callable is only the beginning.
Software can choose a service while it is completing a task. For that decision to be programmatic, the service also needs to be discoverable, understandable, priced, payable, and described by a predictable request contract.
Mahshar connects those requirements through its public Marketplace and agent discovery endpoint. Its OpenAPI document describes how clients use the public machine interface.
THE MARKETPLACE LAYER
What Mahshar handles.
The provider continues to run the upstream service. Mahshar handles the implemented marketplace path around discovery, payment-aware access, and seller accounting.
Discovery
A public Marketplace and machine-readable discovery for eligible active listings, plus an OpenAPI description of Mahshar’s public machine interface.
Pricing
A provider-configured listed base price for each paid call.
Payment flow
The implemented x402 requirement, authorization, verification, and accounting path.
Access
Payment-aware proxy execution against the configured request contract.
Credential protection
Stored seller credentials are omitted from public discovery and buyer-facing listing data, then injected server-side when the configured listing requires them.
Earnings
Accounted paid calls feed the existing seller earnings and withdrawal interfaces.
PROVIDER CONTROL
You control the service and configure the listing.
You control the upstream API and listing configuration. Activation remains subject to Mahshar’s verification and marketplace health safeguards.
Your upstream API
The endpoint and infrastructure remain yours.
Listing status
You can activate or deactivate an eligible listing; verification and marketplace health safeguards still apply.
Listed base price
You set the listed base price per call; current buyer and seller amounts are shown before publication.
Presentation
You manage the name, description, and category.
Request contract
You configure the supported method and declared buyer inputs.
Authentication
You choose the supported public, API-key, bearer, or query-credential mode.
FEES & PAYOUTS
Know the buyer total and your seller share before you list.
You set the listed base price per call. Buyers currently pay that price plus 10%, and Mahshar records 90% of the listed base price as your seller share.
- No listing, publication, or subscription fee in the current listing path.
- Minimum seller withdrawal: 1 USDC.
- Estimated Arc gas is deducted from the requested withdrawal amount.
YOU DO NOT NEED TO UNDERSTAND X402 FIRST
You provide the API. Mahshar handles the marketplace payment layer.
Mahshar is designed to let providers list an existing API without rebuilding its own billing flow around x402. The Seller application asks for the endpoint and the listing information Mahshar actually needs, while the buyer-facing x402 exchange remains part of Mahshar’s Marketplace flow.
This is not a promise of zero configuration: the request contract, authentication mode, public metadata, and price still need to be accurate.
CURRENT PROVIDER FLOW
From endpoint to active listing.
The production Seller application uses a focused workspace rather than a generic submission form. Publication depends on the current endpoint and request-contract checks passing.
- 01
Connect
Connect the EVM wallet used to own the listing. The wallet flow may select Arc Mainnet and uses a signature to sign in.
- 02
Analyze
Paste the public HTTPS endpoint. Analyze sends one real representative request using the configured method, inputs, and credential.
- 03
Configure
Review the name, category, HTTP method, authentication mode, and description.
- 04
Describe the request
Confirm body behavior and any declared path or query inputs buyers may send.
- 05
Price and preview
Set the listed base price per call, review the buyer total and seller share, and preview the Marketplace presentation.
- 06
Publish
Mahshar saves the listing, verifies the persisted endpoint configuration with another representative request, and activates it when the checks pass.
WHAT HAPPENS TO MY CREDENTIALS?
Configured credentials stay out of public listing data.
Credentials are encrypted before database storage, omitted from public discovery and buyer-facing listing data, and not returned after storage. Mahshar decrypts them server-side only where analysis, verification, or proxy execution requires them.
Read provider documentationPROVIDER FAQ
The practical questions, answered plainly.
These answers describe Mahshar’s current production behavior. They do not promise revenue, endpoint performance, or geographic availability.
Do I need to rebuild my API?
Mahshar is designed to list an existing HTTPS API endpoint. You configure how Mahshar may call it; your direct integration and infrastructure remain separate.
Do I need to understand x402 first?
No prior x402 expertise is required to begin the provider flow. The Seller interface collects the endpoint, request contract, authentication mode, public metadata, and listed base price Mahshar needs.
Can my API use API-key or bearer authentication?
Yes. The current listing flow supports public access, an API key in the x-api-key header, bearer authentication, and a configured query credential.
What fee does Mahshar take, and is my listed price what the buyer pays?
You set the listed base price. Buyers currently pay that price plus 10%, while Mahshar records 90% of the listed base price as your seller share. The difference is the platform accounting share.
Does listing cost anything?
The current listing path has no listing, publication, or subscription fee. Paid-call and withdrawal economics still apply.
When can I withdraw earnings?
A seller share becomes available after its paid call is durably accounted. The minimum withdrawal is 1 USDC, and estimated Arc gas is deducted from the requested withdrawal amount.
Does Analyze make a real request, and why can Publish test again?
Yes. Analyze sends a representative request to the endpoint you configure. Publish checks the persisted configuration again before activation so the active listing matches what Mahshar tested.
Can I edit or deactivate the listing later?
Yes. You can edit or deactivate it from the seller interfaces. Endpoint, authentication, or request-contract changes clear verification and deactivate the listing until the saved configuration is checked again.
What happens if my API repeatedly fails?
Marketplace health safeguards can deactivate a repeatedly failing listing. You remain responsible for upstream availability, quotas, capacity, and the effect of Mahshar traffic on your service.
What happens to my upstream credentials?
Credentials are encrypted before database storage, omitted from public discovery and buyer-facing listing data, and not returned after storage. Mahshar decrypts them server-side only where analysis, verification, or proxy execution requires them.
Can AI agents discover my API?
Eligible active listings can appear through Mahshar’s machine-readable agent discovery. The OpenAPI document describes how clients use Mahshar’s public machine interface.
What does the buyer pay with?
Mahshar’s current paid-call architecture uses USDC through its x402 flow on Arc Mainnet.
Which network does Mahshar use?
Mahshar’s implemented production payment contract targets Arc Mainnet.
Can I continue serving customers outside Mahshar?
Yes. Mahshar does not replace or modify your existing direct customer integrations. It adds another access path whose traffic still uses your upstream service.
How do I get started?
Open the Seller application, connect an EVM wallet, sign in, paste the endpoint, and follow the analysis, configuration, pricing, and publish flow.
TECHNOLOGY CONTEXT
Learn about the wider agent-payment ecosystem.
These resources explain technologies used by Mahshar’s current marketplace payment layer.
START SMALL
Start with one endpoint.
You don’t need to move your API business to Mahshar. List a single API endpoint, set a pay-per-call USDC price, and use Mahshar as an additional distribution channel for builders and autonomous agents. Your existing backend, customers, subscriptions, and direct integrations remain yours.
List one endpoint and see how Mahshar works alongside your existing business.