CIDSync is agent-ready.
CIDSync is built to be legible to AI agents and their operators. An agent can fetch a machine-readable offer and configuration checklist, authenticate with a per-account API key, check an account’s readiness and latest dry-run, and assemble a purchase intent. A named human completes checkout and accepts terms (autonomous charging is intentionally off), and provider credentials are entered only in the secure dashboard.
Agent-initiated, human-approved. Autonomous purchase is off by design.
Tracking numbers multiply faster than anyone can register them.
Field-service companies spin up new ServiceTitan tracking numbers constantly; every campaign and acquisition adds numbers and tenants. New numbers go out unregistered, so carrier reputation engines label them “Spam Likely” and answer rates drop. CIDSync is the automation layer between ServiceTitan and the Hiya Connect branded-caller registry: it keeps every tracking number registered and in sync, nightly, across every tenant. That is exactly the kind of recurring, rules-based operational spend that a buying agent or an ops tool is suited to research, configure, and prepare, so we publish the interfaces for it.
Discover. Authenticate. Check readiness. Assemble intent.
1. Discover
An agent fetches the discovery document first. It lists the product, pricing, endpoints, authentication scheme, and states plainly that autonomous purchase is not supported.
2. Read the offer
Two public, unauthenticated endpoints return the machine-readable offer (pricing bands, claims, no-guarantees) and the configuration checklist an account needs before going live.
3. Authenticate
With a per-account API key, issued by a human in the CIDSync dashboard under Settings, an agent can check an account's configuration readiness and its latest dry-run status. Read-only; nothing is written.
4. Assemble a purchase-intent
An agent can package an organization, plan, and buyer into a purchase-intent. The response is a human-approval checkout handoff, not a charge. No Stripe object is created and no subscription activates from this call.
What an agent can do, and what stays human.
What an agent can do
- Fetch the discovery document, offer, and configuration checklist without authentication.
- Authenticate with a per-account API key issued by a human in Settings.
- Check an account’s configuration readiness and its latest dry-run status.
- Assemble a purchase-intent that returns a human-approval checkout handoff.
What always stays human
- Completing checkout and accepting terms. No subscription activates from an agent request alone.
- Entering ServiceTitan or Hiya credentials. They are collected only in the secure dashboard, never via the agent API.
- Charging a card.
autonomous_purchaseisfalsein the discovery document, and a purchase-intent creates no Stripe object. - Initiating a live, credentialed ServiceTitan sync. That runs only in the secure CIDSync pipeline.
The facts, precisely
A purchase-intent returns a checkout handoff for a named human buyer to complete. It never charges a card and never activates a subscription on its own.
Keys are issued in the dashboard under Settings, shown once, and stored only as a hash. Scopes are granted individually: read (account status), config (dry-run status), and purchase (key-authenticated intent).
120 requests per minute per key, enforced on every authenticated call.
Agent-assembled purchase-intents must echo terms version 2026-07-08, the same terms a human buyer accepts at checkout.
Researching CIDSync on behalf of an operator?
Point your agent at the discovery document, or have a human get started directly. Either way, a named person completes checkout.
CIDSync is an independent product. It is not affiliated with, endorsed by, or sponsored by ServiceTitan, Hiya, First Orion, TNS, or any carrier. Autonomous purchase is not supported; a named human always completes checkout and accepts terms.