Surgemesh frequently asked questions
Surgemesh is an agent-first social publishing API that charges $0.02 per delivery, adjusted by dynamic pricing from 0.8x to 3x. Payments are not switched on yet during the beta, but the free sandbox works now. Below are direct answers about pricing, payments, networks, agents and security.
What is Surgemesh?
Surgemesh is an agent-first social publishing API. AI agents and developers use one REST and MCP interface to schedule, publish, list and cancel social posts across brands, and they see the exact dynamic price of each delivery before they commit.
Which social networks does Surgemesh support?
Surgemesh publishes natively to Facebook Pages and Instagram. Set "network" to "facebook" (with a page_id credential) or "instagram" (with an ig_user_id credential) when you connect a channel. No other networks are available today.
How much does Surgemesh cost?
The base price is $0.02 per delivery, multiplied by the price multiplier of the 15-minute slot you schedule into. Multipliers run from 0.8x in quiet slots to a 3x cap in full slots, so one delivery costs between $0.016 and $0.06. Live accounts also get 50 free deliveries every month. Credit is prepaid in packs and never expires.
What is a delivery?
A delivery is one post sent to one channel. It is the unit Surgemesh bills. One post scheduled to a Facebook Page and an Instagram account counts as 2 deliveries.
How does dynamic pricing work?
Each 15-minute slot has a load: the deliveries already booked in that slot, including yours, divided by slot capacity. Below 20% load the multiplier is 0.8x, below 60% it is 1x, and above that it rises linearly to 3x at 100%, rounded up to the next 0.25. GET /v1/quote returns the multiplier, the price and, when the multiplier is above 1, up to 3 cheaper_slots within one hour.
Do prices go up during emergencies?
No. We never raise prices during a declared emergency or disaster. While a government emergency declaration affects our service, every multiplier above 1x is capped at 1x; off-peak discounts still apply.
Can the price change after my post is accepted?
No. The price is locked when POST /v1/posts accepts the post, and the response returns the locked multiplier and price_usd. To protect yourself from price peaks, send max_price_usd: if the locked price would exceed it, the API rejects the post with 409 price_above_max and charges nothing.
How do I get an API key?
Send POST /v1/signup with an email address and "accept_terms": true (name and brand are optional). The 201 response contains your tenant_id, a first brand_id and an api_key with read, write and admin scopes. The key is shown once, so store it immediately. Signup is limited to 3 per IP address per day.
What is the sandbox?
The sandbox is the free starting plan for every new account. It accepts and fully validates posts, including channels, media URLs, scheduling and pricing, but it never publishes anything and never charges. Sandbox posts get the state "sandboxed", and each sandbox account can create up to 100 posts per month.
Are payments switched on during the beta?
Not yet. During the beta, payments are not enabled: GET /v1/pricing reports "payments_enabled": false, and POST /v1/billing/topup returns HTTP 503 with the error payments_not_enabled. The sandbox works now, so you can sign up, connect channels, quote and create posts end to end without paying.
How do I go live?
Your first credit top-up switches the account from sandbox to live. Any pack works. Because payments are not enabled during the beta, top-ups are not possible yet; once they are, live accounts publish to real channels and receive 50 free deliveries every month.
How will I pay for Surgemesh?
With prepaid credit packs paid in USDC on Base through the x402 protocol: pack_5 (pay $5, get $5 credit), pack_20 (pay $20, get $22) or pack_100 (pay $100, get $120). Payments settle into Stripe, which holds and converts them; an agent with a wallet can pay without a human. Card payments are coming soon. Credits expire 5 years after purchase. Credits are for business use, are promotional non-cash value, cannot be transferred or cashed out, and work only on Surgemesh.
What happens when my credit runs out?
POST /v1/posts answers HTTP 402 with the error insufficient_credit, and the post is not created. Once payments are enabled, that 402 body is an x402 offer for pack_5 whose resource is the top-up endpoint; until then it is a problem+json error that includes a quote. Free monthly deliveries are always used before credit, and failed deliveries are refunded to credit automatically.
Does Surgemesh support MCP?
Yes. POST https://api.surgemesh.com/mcp is a stateless JSON-RPC 2.0 MCP server (protocol version 2025-06-18, JSON responses, no SSE). It exposes get_pricing, get_quote, list_channels, list_brands, create_post, list_posts, cancel_post and get_usage, and it uses the same Bearer API key as the REST API.
How do AI agents discover Surgemesh?
Agents can read https://surgemesh.com/llms.txt and https://surgemesh.com/llms-full.txt, fetch the OpenAPI document at https://api.surgemesh.com/openapi.json, or read the A2A agent card at https://api.surgemesh.com/.well-known/agent.json. MCP clients can connect directly to https://api.surgemesh.com/mcp.
Why does POST /v1/posts require an Idempotency-Key?
Agents retry, and networks fail. Creating a post is the one write that could duplicate a publish and a charge, so it requires an Idempotency-Key header (or an idempotency_key body field). The same key with the same body returns the original result with "idempotent_replay": true; the same key with a different body returns 409 idempotency_key_reused. Other writes do not need a key.
How are channel credentials and API keys protected?
Channel credentials are encrypted at rest and never returned by the API, and disconnecting a channel erases them. API keys are shown once, carry explicit scopes (read, write, admin), can be limited to specific brands, can expire and can be revoked at any time. Requests are rate limited per IP, per key and at the edge.
Can I cancel a scheduled post?
Yes. DELETE /v1/posts/{id}, or the cancel_post MCP tool, cancels the deliveries that are still queued and returns refunded_usd. If nothing is still queued, the API returns 409 post_not_cancelable.
Can one account manage several brands or clients?
Yes. Each account is a tenant with up to 25 brands, each with its own channels. You can mint up to 50 active keys, give each agent or client only the scopes it needs, and restrict each key to specific brands.