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
Start with the marketplace, provider onboarding, agent discovery, Arc Mainnet x402 contract, purchase access, or Wallet funding flow.
BROWSE BY TOPIC
Every destination below is an implemented route or a section on this page.
Choose the implemented buyer, provider, or agent path.
Stateless discovery, x402 preparation, signed execution, and recovery.
Discovery, proxy styles, payment, and delivery states.
List an endpoint and complete the existing review flow.
Read the Arc Mainnet x402 v2 request sequence.
See how configured seller auth is applied by the proxy.
Purchase capabilities, delivery states, and reconciliation.
Bridge to an Arc wallet, then deposit explicitly if needed.
Open the implemented public OpenAPI 3.1 document.
GETTING STARTED
Mahshar provides separate interfaces for people buying API calls, providers listing endpoints, and autonomous clients.
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.
The provider keeps operating the upstream service. Mahshar collects the endpoint, request contract, authentication mode, public metadata, and listed base price for its separate listing and access path.
The agent path starts with the public discovery endpoint, which links the OpenAPI contract and describes each active listing.
AGENT INTEGRATION
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/yamlMCP V1 PHASE 2
Connect an MCP client to https://mahshar.xyz/api/mcp. search_apis and get_api use the safe public discovery contract. An unsigned execute_api_call returns the real 402 challenge and a short-lived prepared-call token; the MCP host must validate the challenge and sign it with its own wallet before replaying the exact prepared arguments. Mahshar never accepts private keys, signs automatically, or takes custody. get_purchase_response retrieves one exact paid response using the returned bearer purchase capability. The external MCP path is Production-verified for discovery, external signing, Arc Mainnet settlement, paid execution, persistent recovery, same-authorization replay without duplicate settlement or provider execution, and buyer, seller, and platform accounting. Browser and UI flows were not part of that verification.
endpoint POST https://mahshar.xyz/api/mcp
transport stateless Streamable HTTP
tools search_apis, get_api
execute_api_call
get_purchase_response
signing external wallet required
custody none
recovery returned purchase capabilityPAYMENT, AUTH & ACCESS
These behaviors are declared in the proxy routes, agent discovery response, OpenAPI document, and purchase-access implementation.
Payment-Signature.PAYMENT-REQUIRED header from the 402 response.WALLET FUNDING
The dashboard exposes both operations without combining their transaction paths.
The Bridge page discovers official Circle routes for supported Mainnet source wallets and targets the connected EVM wallet on Arc Mainnet.
The Solana to Arc page moves supported SPL USDC from the connected Solana source wallet to the connected EVM wallet on Arc Mainnet.
The Wallet deposit is a separate, explicit action from USDC already held by the connected EVM wallet on Arc Mainnet.
Use the self-service support topics or contact the verified Mahshar support address.