API and MCP for partners
Hand tasks over to me straight from your software and AI assistants: send the task, get a price and a deadline, accept, and I start the work. The same API serves the catalogue of my 8 services.
Ordering through the API
No API key is needed. A new order returns an order number and an order key: use them to read the status and to reply. The same actions are available through MCP using the create_order, get_order and order_action tools.
- You send the task: POST /api/orders. Status: received.
- I read the task and post a price and a deadline into the order. Status: quoted.
- You accept the price (accept with the quote number, quote_id), decline it (decline) or ask a question (message).
- After you accept the quote, I start work: status in_work, then delivered with a link to the result.
- You approve the work (approve) - status closed, or return it with remarks (revision) - the order goes back to in_work.
POST /api/orders | New order. Required: task (up to 4000 characters), contact and consent: true. Optional: title, partner, ref (your own task number), deadline, budget, service, links (up to 5 https links), lang, callback_url, idempotency_key. |
|---|---|
GET /api/orders/{id} | Status, price and deadline (quote), results (deliverables), events, the steps available now (actions) and a hint on what to do next (next). Requires the Authorization: Bearer header with the order key. |
POST /api/orders/{id} | Your step: action - accept (requires quote_id from quote.id), decline, cancel, approve, revision or message; message and revision require text. Same header. |
curl -X POST 'https://fastdev24.com/api/orders' \
-H 'Content-Type: application/json' \
--data '{"task":"Landing page for a dental clinic: 5 sections, enquiry form, texts attached.","contact":"dev@example.com","consent":true,"ref":"TASK-17","idempotency_key":"<random-hex-64>","links":["https://example.com/brief.pdf"]}'
curl 'https://fastdev24.com/api/orders/ORDER_ID' -H 'Authorization: Bearer ORDER_KEY'
curl -X POST 'https://fastdev24.com/api/orders/ORDER_ID' \
-H 'Authorization: Bearer ORDER_KEY' -H 'Content-Type: application/json' \
--data '{"action":"accept","quote_id":"QUOTE_ID"}'
To get notified when the order changes, pass callback_url: I POST the order number, status and price to that address whenever I update the order. The request is signed with the order key (X-Order-Signature header) and tried twice; if your address does not answer, you can always read the state with GET. To make a retry safe, pass idempotency_key - your own random string of at least 16 characters: a retry with it returns the same order.
Service catalogue
Read-only, no API key required. The lang parameter sets the response language: ru, pl, en, de, es or fr (default: en). Responses are JSON with an ETag and are cached for 5 minutes.
GET /api/services?lang=en | List of services: number, slug, group, title, result, turnaround and price where published. |
|---|---|
GET /api/services/{id}?lang=en | One service by number 1-8 or slug, e.g. web-design: scope, what I need from you, checks, acceptance, FAQ. |
GET /openapi.json | OpenAPI 3.1 specification of the API. |
curl 'https://fastdev24.com/api/services/web-design?lang=en'
MCP server
Endpoint: https://fastdev24.com/mcp. Stateless Streamable HTTP transport (no sessions): protocol version 2026-07-28 and the earlier initialize-based versions 2025-11-25, 2025-06-18. Responses are plain JSON; there is no SSE stream over GET.
Tools
list_services- list of services in the chosen language, optionally filtered by groupget_service- full details of one servicecreate_request- an enquiry to me: contact details, a task description of up to 600 characters and acceptance of the privacy policycreate_order- a new order: task, contact and consent; returns the order number and keyget_order- order status, price and deadline, results, eventsorder_action- accept the price, decline it, cancel the order, approve the work, return it for revision or send a message
How to connect
In a client that supports remote MCP servers, add a server with the endpoint above. Example for Claude Code (.mcp.json):
{
"mcpServers": {
"fastdev24": {
"type": "http",
"url": "https://fastdev24.com/mcp"
}
}
}
Command-line example: list the tools. For version 2026-07-28, include the protocol version and client capabilities in _meta:
curl -X POST 'https://fastdev24.com/mcp' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2026-07-28' -H 'Mcp-Method: tools/list' \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{}}}}'
Limits
- New orders: about 20 per hour per IP address and about 100 per day in total. Request body: up to 32 KB for a new order, 16 KB for a step. Per order: up to 60 steps per hour and 20 messages per day. Keep the order key: the order cannot be read without it. Orders are stored for 180 days after the last change. Poll the status no more often than once every few minutes. If a delivered result gets no answer for 7 days, I close the order.
- Enquiry limits are best-effort: about 10 per hour through the form and 30 through MCP per IP, and about 60 per day overall. They may not hold during failures or concurrent requests.
- Send an enquiry only after the person explicitly agrees: the contact details and task reach me exactly as if sent through the website form.
- MCP tool calls are limited to about 60 per minute per IP per server instance. Maximum request body sizes are 64 KB for MCP and 16 KB for the form.
- API responses include 400 (bad_lang, bad_group), 404 (not_found), and 304 when the ETag matches. create_request input errors return isError with an explanation.
- The catalogue is updated together with the website; a new version value or ETag for the same resource and language means the data or response format has changed.