Developers
Build on the Envoy platform.
Authorized APIs and agent tools for connectivity commerce: catalog, coverage, quotes, orders, dispatch, field evidence, equipment, support and policy evaluation.
Access is scoped to an organization, a role and a purpose. A token is not a blank cheque.
Capability families.
Catalog
Products, providers, eligibility rules and approved offers.
Coverage
Address-level serviceability checks and their confidence state.
Quotes
Draft and retrieve structured commercial options.
Sales
Leads, assessments, opportunities and attribution.
Orders
Prepare an order and submit only after approval.
Dispatch
Eligible technicians, availability and assignment drafts.
Field
Scoped completion evidence and test records.
Equipment
Inventory, custody, reservations and returns.
Support
Cases, status and escalation.
Finance
Restricted invoice, payment and commission records.
Training
Courses, competencies and certification status.
Policy
Evaluate whether an action is permitted and what approval it needs.
Access is scoped, not ambient.
The platform is multi-tenant. Isolation and least privilege are product requirements, not deployment options.
- Strong authentication and short-lived tokens
- Resource-specific authorization
- Tenant isolation by organization
- Explicit tool scopes and allowlists
- Environment separation: sandbox, staging and production
- Rate limits and idempotent commands
- Execution traces and receipts
- Evaluation tests for agent behavior
Agent onboarding.
Discover capabilities
Read the capability catalog and available scopes.
Authenticate
Establish an accountable identity for the agent and its organization.
Select the tenant
Choose the organization and role context the agent may act within.
Confirm eligibility
Check provider, territory and product eligibility before promising anything.
Draft and request
Prepare a quote, order or assignment for the required approval.
Execute within limits
Perform only the bounded action that was authorized.
Record the receipt
Store what was requested, permitted, executed and reviewed.
Read-only first.
The first useful integration is a capabilities or serviceability query—not an autonomous purchase.
Agent-to-agent communication must pass typed requests and status without silently broadening authorization or forwarding provider credentials.
Start with a query, not a purchase.
Request access, identify the accountable organization and begin with a read-only capability in the sandbox.
APIs, MCP tools and sandbox environments are proposed or in development. No production API availability, rate limit or service level is promised by this page.