Build on the factory floor
Realme exposes the same capabilities the site uses — search, prepare a design, publish it, order it, follow it — over an API, an MCP server for agents, and webhooks for events. This is the starting point.
Last updated August 2026
Interfaces
Pick the surface that fits how you build.
Connect Claude, a custom GPT, or a LangGraph worker. Scoped keys, per-call metering, full audit trail.
Predictable REST endpoints with JSON, bearer auth, and paginated lists.
Get notified on order placed, printed, shipped, and delivered.
Typed clients that wrap the API and handle auth and retries.
The 8 tools
The same toolset your agent gets over MCP and REST.
Query the live catalogue — 9 families, 46 products — with server-authoritative base prices, lead times and customs zones.
Start a customization session: product, options, destination and complexity tier, with the reference image attached.
Attach a reference image to an existing session. Content-sniffed, hashed, stored privately.
Render the 2D concept preview — only after a human COMPLIANCE reviewer approves the reference.
Read the session: status, assets, previews and the current quote.
Publish an approved design so it can be quoted and ordered.
Place an order. The amount is computed server-side — the agent never sends one.
Follow the order through production, quality check, shipment and delivery.
Authentication
Every request is authenticated with a scoped API key (REALME_API_KEY). Keys carry per-key permissions and metering so you can grant an agent exactly the access it needs and watch what it does.