Skip to content
Developer sandbox

BUILD FOR THE CUSTOMER’S OWN AGENT

Real businesses.
Real questions.
Less repetition.

Help someone find a small business and prepare a useful quote request, using the assistant they already trust.

Explore the quote flow Find a business ↗

01 / CHOOSE THE RIGHT SCOPE

Discovery first. One business at a time.

Public discovery

Network connection

Search participating businesses and prepare a public shortlist. Explain coverage and fit. The customer chooses the recipient.

/mcp

On the network’s published directory hostname. Never send a private brief, contact details or receipts here.

Browse the directory →
Chosen business

Business connection

Read approved facts and current questions, prepare a private draft, and hand off to the customer for review.

/.nexttyr/mcp

On the business’s verified website hostname. Confirm a new connection with the customer before sharing facts.

For multiple recipients, keep each draft and receipt separate.

02 / FROM INTENT TO A USEFUL REQUEST

Read the form. Respect the person.

  1. Discover

    Start with the service and location. Show participating businesses, why each fits, and what remains unknown. Let the customer choose.

  2. Read

    Use the chosen business’s connection card. Check its business ID, current release, tool catalog and request requirements before sharing private facts.

  3. Prepare

    Ask which known facts the customer permits you to reuse. Map them to the real question IDs, types and options. Ask only applicable missing or uncertain questions.

  4. Review

    Create a private draft and prepare_customer_review. Open the returned link on the business website so the customer can correct answers and choose contact permissions.

  5. Follow through

    Keep the receipt paired with its business. Report the returned status faithfully. An approved quote is separate from a request, booking or payment.

A private draft is not a submission.

Agents cannot send the final quote request through an MCP tool. The customer reviews the exact answers and selected contact channels on the business website. Never infer consent from an earlier conversation.

03 / NO HTML SCRAPING REQUIRED

The live form is the contract.

Read the current tool catalog and schema from the chosen business. Preserve conditional rules, stable question IDs, answer types, option IDs, revision and document hash. A similar label is not an interchangeable answer.

Read quote requirements · MCP 2025-11-25

Replace business.example with the verified business hostname. This reserved example is not a live endpoint.

curl https://business.example/.nexttyr/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Mcp-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/call",
    "params":{"name":"get_request_requirements",
      "arguments":{"action":"request_quote"}}}'

Machine-readable discovery

On each participating business origin:

/.well-known/api-catalog
RFC 9727 links to the API description.
/.well-known/agent-api.json
Current HTTP operations in OpenAPI 3.1.
/.well-known/quote-requirements.json
The published request schema and release.

These are paths on the chosen business website, not this developer page. Unsupported or paused intake must fall back to that website.

Boundaries to build around

  • MCP versions: 2026-07-28 and 2025-11-25. Negotiate the version supported by your host.
  • Private input: at most 65,536 UTF-8 bytes, including the customer request envelope.
  • Business edge limits: 180 requests per address/business and 600 per business per 60 seconds. These are local edge safeguards.
  • Public reads need no NextTyr customer login. Keep draft/session and receipt capabilities private.
  • Customer/provider credentials stay in their own trusted application. Never put them in endpoint URLs or quote answers.
Handle retries and changing requirements
409 · Requirements or revision changed
Read the current draft and schema, preserve customer corrections, repair the affected answers and request a fresh review.
413 · Input too large
Reduce the payload. Do not truncate contact details or silently discard required answers.
429 · Rate limit
Honor Retry-After. Avoid parallel write bursts.
Timeout or unavailable response
The write may have happened. Read the known draft or receipt first; never blindly recreate or resubmit it.

Use the server’s X-NextTyr-Request-Id with support. Do not share private answers, draft/session tokens or receipts.

04 / TRY THE WHOLE PATH SAFELY

Local sandbox

Two clearly synthetic businesses, real schemas and disposable test receipts. The local harness runs the quote workflow against an isolated PostgreSQL cluster with external delivery blocked.

Development access is free and capped. The harness requires repository access, Node.js, installed PostgreSQL tools and the project dependencies. Contact support for the developer package.

Request developer access ↗

Start with synthetic facts

  1. Run npm run discovery:sandbox in the developer package.
  2. Use the generated local credential file with the documented walkthrough. Never use a provider key or real customer details.
  3. Discover → read schema → prepare → review → confirm → read test receipt.
  4. Restart to erase the run and rotate credentials. Old capabilities belong to the discarded run.

Local harness results describe that exact version and environment. Hosted sandbox access and Registry publication remain pending.

05 / USE THE CUSTOMER’S OWN ACCOUNT

Specific surfaces. Honest status.

Official guides for four developer APIs, reviewed October 4, 2026. API documentation and local tests do not establish compatibility with a customer app, model, account or region.

Record exact product/build, model, protocol version, account eligibility, region, language and test date. App UI, elicitation and Tasks need their own observations. Use website continuation when a capability is unsupported.

BUILD SOMETHING USEFUL FOR SMALL BUSINESS

Let’s make the next step easier.

Integration partners agree on operator identity, permitted use, customer disclosure, scope and revocation before access is granted. Outreach and enrollment are separate from a passing local test.

Contact developer support ↗
PrivacyTerms