For AI agents
Built for people.Open to agents.
Your agent can read our catalog, price an order and place it, over a plain JSON API or MCP. A person at LinkHatch replies by email, and nothing is placed until a human approves the sites.
Connect in one line
Add the MCP server to any MCP client, or call the order endpoint directly.
MCP client config
{
"mcpServers": {
"linkhatch": { "type": "http", "url": "https://linkhatch.com/api/mcp" }
}
}Response
{
"ok": true,
"order_ref": "LH-261008-3FA2C1",
"status": "awaiting_confirmation",
"estimate": { "totalUsd": 2500, "interval": "one-off",
"lines": ["5 x Plus link at $500"] },
"checkout_url": null,
"confirmation": { "sent_to": "s***@client.com",
"expires_at": "2026-10-11T09:00:00.000Z" },
"next_steps": ["We emailed s***@client.com a link to confirm this order. ..."]
}REST
curl -X POST https://linkhatch.com/api/order \
-H "content-type: application/json" \
-H "idempotency-key: order-7f3a" \
-d '{
"kind": "links",
"tier": "plus",
"quantity": 5,
"site": "client.com",
"niche": "edtech",
"email": "seo@client.com",
"agent_name": "Acme SEO agent"
}'Where agents look
Everything an agent or answer engine needs, at the usual addresses.
- /llms.txt
- Who we are, what we sell, prices and how to order, in plain text.
- /llms-full.txt
- Every service page, policy and answer in one file.
- /api/catalog
- Tiers, plans, agency rates, PR prices and policies as JSON.
- /openapi.json
- OpenAPI 3.1 schema for the catalog and order endpoints.
- /api/mcp
- MCP server: get_catalog, estimate_price, place_order.
- /.well-known/agent-card.json
- Agent card describing the same skills.
What an agent order does
The owner confirms by email
We email the address in the order a link to confirm it. Nothing is placed, charged or sent to anyone until they press Confirm. The link works for 72 hours.
Nothing is charged by an order
An order is a request. Once confirmed, we reply to the human's email with the sites to approve or a quote.
A human approves every site
DR, traffic, the page and the cost of each site, before any outreach.
Plans go to checkout after confirming
For monthly plans, pressing Confirm takes the human straight to Stripe checkout. Agents don't pay on their own.
Quote the reference, retry safely
Every order gets an order_ref; use it in any email to mariana@linkhatch.com. Send an Idempotency-Key header (MCP: idempotency_key) and a retry won't send a second email.
Fair questions
- Can my AI agent order backlinks from LinkHatch?
- Yes. It can call POST /api/order or connect to our MCP server at linkhatch.com/api/mcp. We email the human a link to confirm the order; then we reply with sites for them to approve.
- Does the agent need an API key?
- No. Reading the catalog and placing an order are open. The owner of the email confirms each order from a link we send them, nothing is charged by an order, and every site is approved by a person before work starts.
- Which agents work with it?
- Anything that speaks HTTP and JSON, plus any MCP client such as Claude, ChatGPT connectors, Cursor or your own agent framework.
- Can an agency's agent order for several clients?
- Yes. Send one order per client domain with on_behalf_of set to the client. Receipts stay separate per client, and white-label receipts carry the agency's name.
- How does payment work?
- Incify, which runs LinkHatch, bills through Stripe. Monthly plans are paid at Stripe checkout right after the owner confirms; single links and PR are invoiced when they go live or run.
Rather talk to a person?
We answer within working hours, Singapore time.