For AI
agents

Quick start

$ claude mcp add --transport http chnlsync https://mcp.chnlsync.com/mcp
# no key needed for the MCP endpoint

$ curl "https://api.chnlsync.dev/api/v1/copper-retirement?carrier=AT%26T&state=TX"
# keyless public route · FCC-sourced · CC BY 4.0 · cite source_url
$ 

Two things work with no credentials at all: the MCP endpoint and the public copper retirement route. The REST mirror of the advisor takes a per-consumer key (see Getting a key). Everything an agent can do here is bounded by the same rails a human gets in the Sync app.

What Sync is

Sync turns a plain-language description of what is not working — a copper retirement letter, a phone system at end of life, a renewal that feels expensive — into a structured case file, and keeps a living record of the buyer’s environment so nothing has to be re-explained. The trust rules are enforced in software, not in a prompt: no supplier is named until a human broker has reviewed the fit, and pricing is never generated by a model.

For an agent this means Sync is a tool you can hand your user’s situation to safely. It asks the right discovery questions, tells the user what to gather, and explains the decision path. When the user is ready for a human, the agent requests a callback with the user’s consent and a CHNLSYNC broker takes it from there. Each advisor reply also returns a claim_url; the user can take over the workspace at any point and continue in the Sync app at app.chnlsync.com, with everything gathered so far carried across.

CHNLSYNC receives supplier compensation for its brokerage service and charges no buyer advisory fee. Your service contract is with the supplier. You still pay for supplier services, and equipment, installation or separately scoped work can carry charges. Ask for the compensation model and a complete cost breakdown before choosing an option.

REST mirror

The same three actions are plain HTTPS routes. Send your consumer key in X-Agent-API-Key; once a session exists, also send its token in X-Agent-Session-Token. Bodies and responses are JSON. The public copper route is the exception: no key, no session.

Create a session

curl -X POST https://api.chnlsync.dev/api/v1/agent/sessions \
  -H "X-Agent-API-Key: $CHNLSYNC_AGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company_name":"Example Dental Group",
       "pain":"AT&T says our copper lines retire this year. Four offices, fax and alarm lines on POTS."}'

Ask the advisor

curl -X POST https://api.chnlsync.dev/api/v1/agent/sessions/$SESSION_ID/chat \
  -H "X-Agent-API-Key: $CHNLSYNC_AGENT_API_KEY" \
  -H "X-Agent-Session-Token: $SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"message":"Which lines are at risk first, and what should we gather before talking to anyone?"}'

Response (sketch)

{
  "assistant_message": "Start with the lines that cannot fail: the fire panel and the elevator phone ...",
  "follow_up_questions": ["Which office received the letter?", "Do any lines carry a fax or alarm?"],
  "conversation_id": "89c56588-3e6a-4558-9b48-fca1960d86ae",
  "review_status": null,
  "claim_url": "https://app.chnlsync.com/portal?claim=...",
  "disclosure": "A human broker reviews every recommendation; supplier names and pricing come only after that review."
}

Continue the same conversation

Copy the conversation_id from the preceding reply. With REST, omitting it starts a new conversation. With MCP 0.2.0 and later, incomplete continuation handles are rejected before another workspace is created.

{
  "message": "The renewal date is October 31. What should we gather next?",
  "conversation_id": "89c56588-3e6a-4558-9b48-fca1960d86ae"
}

Example REST follow-up body; replace the illustrated ID with your returned ID. For MCP, include your returned session_id and session_token too. Credentials and claim links are private: never publish them or put them in analytics.

Recover missing handles from the prior reply. Do not automatically create a replacement workspace or retry a write after a timeout: the original request may already be recorded. Use the claim link or contact support if its outcome is unclear.

Request a callback (with consent)

curl -X POST https://api.chnlsync.dev/api/v1/agent/sessions/$SESSION_ID/callback-request \
  -H "X-Agent-API-Key: $CHNLSYNC_AGENT_API_KEY" \
  -H "X-Agent-Session-Token: $SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"contact_name":"Dana Ortiz","contact_email":"dana@example.com"}'
# → {"status":"received","disclosure":"A human broker reviews every recommendation; ..."}

Copper status, no key

curl "https://api.chnlsync.dev/api/v1/copper-retirement?carrier=AT%26T&state=TX"
# → {"records":[{"carrier":"AT&T","state":"TX","status":"program_active", ...}],
#    "source":"FCC Section 214 discontinuance filings ...","source_url":"https://chnlsync.com/copper-retirement/","license":"CC BY 4.0"}

Status codes. 401 unknown or missing key. 404 unknown session, or the agent surface is closed. 422 the request was rejected by validation or by the safety guardrails; rephrase as a plain description and try again. 429 a limit was reached; see Limits.

Getting a key

The MCP endpoint and the public copper route need no credentials. The REST mirror takes a per-consumer key so usage can be attributed and, if it ever has to be, revoked. Email agents@chnlsync.com with who you are, what your agent does, and the volume you expect. Keys are named per consumer and issued by a person, not a form.

Data and license

The copper retirement dataset is licensed CC BY 4.0. Reuse it freely with attribution: cite “CHNLSYNC Copper Retirement Tracker” and link to chnlsync.com/copper-retirement/; the source_url field carries that link for you. Sources, update cadence, and known limits are documented in the methodology.

Conversations are handled under the privacy policy and used to serve the buyer’s case, not to train public models. Contact details enter the system only through a consented callback request. Use of the API is governed by the terms of service.