Buy API access
Browse active APIs on the public Marketplace, then open the existing buyer application when you are ready to connect a wallet and make a call.
MAHSHAR DOCUMENTATION
Documentation for theinterfaces that exist today.
Start with the marketplace, provider onboarding, agent discovery, Arc Mainnet x402 contract, purchase access, or Wallet funding flow.
BROWSE BY TOPIC
Find the relevant product path
Every destination below is an implemented route or a section on this page.
Getting started
Choose the implemented buyer, provider, or agent path.
Agent integration
Discovery, proxy styles, payment, and delivery states.
API providers
List an endpoint and complete the existing review flow.
Payments and x402
Read the Arc Mainnet x402 v2 request sequence.
Endpoint authentication
See how configured seller auth is applied by the proxy.
Access and recovery
Purchase capabilities, delivery states, and reconciliation.
Wallet funding
Bridge to an Arc wallet, then deposit explicitly if needed.
OpenAPI YAML
Open the implemented public OpenAPI 3.1 document.
GETTING STARTED
Three implemented entry points
Mahshar provides separate interfaces for people buying API calls, providers listing endpoints, and autonomous clients.
List an API
The provider flow collects endpoint, method, auth, price, and example data, then uses the existing review and activation path.
Integrate an agent
The agent path starts with the public discovery endpoint, which links the OpenAPI contract and describes each active listing.
AGENT INTEGRATION
Discover first, then follow the selected listing.
The discovery response includes the listing method, proxy URL and style, request metadata, optional schemas and examples, auth type, listed price, payment contract, and response wrapper. Seller upstream URLs and credentials are not part of that public contract.
GET /api/agent/discover
→ active listings
→ proxy_url + proxy_style
→ request + response metadata
→ Arc Mainnet payment contract
→ OpenAPI URL
GET /api/openapi
→ application/yamlPAYMENT, AUTH & ACCESS
The current request contract
These behaviors are declared in the proxy routes, agent discovery response, OpenAPI document, and purchase-access implementation.
x402 v2 payment
- Probe the intended request without
Payment-Signature. - Read the base64
PAYMENT-REQUIREDheader from the 402 response. - Validate and sign the offered Arc Mainnet requirement, then retry the identical request.
Seller endpoint authentication
- Listings can declare public, API-key, bearer, or query-parameter authentication.
- Configured seller auth is injected by Mahshar when the proxy calls the upstream endpoint.
- Buyer-supplied headers are not forwarded upstream.
Purchase access and recovery
- Paid results include a purchase-access capability for response retrieval.
- Only a response marked retryable permits an exact proof and request replay.
- Accounting reconciliation never resettles payment or re-executes the upstream request.
WALLET FUNDING
Bridge receipt and Mahshar Balance are separate steps
The dashboard exposes both operations without combining their transaction paths.
Bridge to Arc
The Bridge page discovers official Circle routes for supported Mainnet source wallets and targets the connected EVM wallet on Arc Mainnet.
Solana to Arc
The Solana to Arc page moves supported SPL USDC from the connected Solana source wallet to the connected EVM wallet on Arc Mainnet.
Deposit to Mahshar Balance
The Wallet deposit is a separate, explicit action from USDC already held by the connected EVM wallet on Arc Mainnet.
Need help with a product flow?
Use the self-service support topics or contact the verified Mahshar support address.