Help with your order.

Tools & request limits

Every price is recomputed on the server from the product configuration — at quote, at draft, and again before checkout. A price sent by a client is ignored. An itemId preserves selections, not a locked price; a changed catalogue can require a new quote and draft.

Rate limits are best effort per server instance, not a guaranteed global quota. Send individual JSON-RPC messages in separate POST requests; batching is an optional server extension.

Draft validity

7 days

Lines per draft

Up to 7

Packages per line

Up to 1000

Artwork links

Up to 10

Order note

1200 characters

Batch extension (optional)

Up to 10 calls

Authenticated customer account

Your work. Its facts. One next step.

Read your linked work and ask the factual support agent about payment, artwork, proof and recorded progress. Your account identity is checked on every request.

{
  "url": "https://angelsprint.com/api/agent/work/mcp",
  "transport": "HTTP JSON-RPC POST",
  "header": "Authorization: Bearer <customer access token from your trusted session integration>"
}

{
  "jsonrpc": "2.0",
  "id": 10,
  "method": "tools/call",
  "params": {
    "name": "list_my_orders",
    "arguments": {
      "limit": 10
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 11,
  "method": "tools/call",
  "params": {
    "name": "ask_work_question",
    "arguments": {
      "workId": "job:<UUID returned by list_my_orders>",
      "question": "What is the recorded status and next step?",
      "clientRequestId": "<new UUID; preserve for retries>"
    }
  }
}

From brief to delivery

1. 01

   Understand the job

   Your AI assistant · Customer

   Collect the product or intended use, finished dimensions, quantity, material/finish, artwork versions, required date and pickup or delivery ZIP. An event date is a requirement, not a confirmed delivery promise.

   Agent action

   Ask for missing details. Read the catalogue and this guide; do not invent a product, option or price.

   Next interface

   For custom fabrication, installation or a non-catalogue specification, use the contact form or email for a shop quote.

2. 02

   Find, configure and price

   search_products → get_product → get_quote

   Read the actual quantity ladder, size limits, options and turnaround names. API dimensions are inches; prices are USD. quantity is pieces per print run; packages on a quote and qty on an order line mean repeated identical runs.

   Agent action

   Show chosen, summary, adjustments, shippingStatus and the returned total. Preserve itemId for the draft. Quantity may be adjusted; an itemId preserves configuration, not a price guarantee.

   Next interface

   Use fulfillment: pickup for free shop collection, or delivery plus the destination ZIP. Delivery costs at least $50; an unknown quote is not a fixed $50 charge. Unknown shipping or a null total must be resolved before promising a final amount.

3. 03

   Collect the right artwork

   artwork[] references · Upload link · Account

   A draft can reference up to 10 HTTPS artwork URLs (480 characters each). The API records references; it does not retrieve, inspect or certify their contents. The separate authenticated private-work API can read customer file metadata; it returns no file bytes or download capability.

   Agent action

   Use only files the customer authorized. Identify the latest source, dimensions and intended sides. Keep shared links accessible to the intended recipient; do not publish customer artwork or capability tokens.

   Next interface

   Use the upload link supplied for that order or its signed-in account upload. Request the correct link if none was supplied; do not invent artwork/proof tokens.

4. 04

   Prepare the purchase for review

   create_order → approval_url → Customer

   Create the draft with an itemId per line, operator.email, fulfillment and any delivery ZIP. Save draft_id and expires_at privately. The signed draft normally expires after 7 days; signing prevents editing but does not encrypt its customer information.

   Agent action

   Return approval_url, the exact configured summary, adjustments and next_step to the customer. No approval email is sent by create_order. Reuse the existing draft for follow-up instead of creating a new one for every status check.

   Next interface

   The customer opens the review page and pays through Stripe. The approval page can collect a missing delivery ZIP or switch to pickup; payment totals are checked again.

5. 05

   Confirm payment independently

   check_order · Customer receipt

   The public status tool reports awaiting_approval, paid or expired. Payment is separate from a proof decision and from physical production. A paid response confirms the payment lookup, not that a parcel is moving.

   Agent action

   Read payment_lookup as well as status. If lookup is unavailable, report payment as unknown and retry later without initiating another payment. Keep draft_id separate from the actual order reference.

   Next interface

   If the customer paid but the result cannot be reconciled, use their receipt and order reference in an authenticated message or the existing email thread.

6. 06

   Validate the file and approve the proof

   Artwork review · Order-specific proof link · Customer

   Receiving a file checks neither print readiness nor customer approval. The shop's file review and the customer's visual approval are separate. A proof link lets the customer inspect the presented version and approve it or request changes.

   Agent action

   Check the file checklist below, keep a clear revision record and explain unresolved issues. Never infer bleed, resolution, fonts or color accuracy from a successful upload. MCP has no preflight or proof-decision tool.

   Next interface

   The customer uses the supplied proof link. If the file or scope changes, obtain review of the new version. Production readiness must be verified from the applicable payment, file and proof records.

7. 07

   Follow the recorded production status

   Linked account order · Order email

   A quote's production-day estimate is not machine telemetry. The current public agent API does not expose printing, cutting, finishing, quality checks, packaging or a production-completion event.

   Agent action

   Keep the deadline and last confirmed update together. Do not turn payment success, a generated proof or a target date into a ready-for-pickup message.

   Next interface

   Check the linked account order where available, or continue the existing order conversation. Wait for an explicit readiness update before arranging collection.

8. 08

   Collect, receive and resolve issues

   Ready notice · Delivery information · Customer

   For pickup, use the shop address and hours after readiness is confirmed. For delivery, use the shipping information actually supplied. The MCP payment-status endpoint does not return carrier tracking or proof of delivery.

   Agent action

   Keep pickup and delivery distinct. A label, estimate or payment is not evidence of receipt. For damage or a production defect, gather the order reference, photos and the customer's description promptly.

   Next interface

   Follow the pickup/shipping and problems/reprints instructions on Customer Service. A completed order needs a confirmed outcome; do not mark it delivered because no further message arrived.

Read a status. Choose the next action.

Troubleshoot a request