CHNLSYNC

CHNLSYNC ("The AI-Native Technology Brokerage", tagline "Advise. Source. Manage.") is a technology brokerage for businesses with 20-500 employees. Buyers describe what is not working - phone systems at end of life, copper line retirement notices, contract renewals, overpriced circuits - and CHNLSYNC builds a case file, researches a network of 300+ suppliers and recommends a path across connectivity, UCaaS, CCaaS, CPaaS, security, SASE, cloud, colocation and CX/voice AI, with a named human broker (founder Will Kennedy) reviewing every introduction. It uses a supplier-paid model with no buyer advisory fee, and publishes a Copper Retirement Tracker with an embeddable widget and JSON feed.

CHNLSYNC publishes 12 API contracts indexed on the APIs.io network, including Copper Retirement API, Customer Agent API, Customer API, and 9 more. Tagged areas include Company, Technology Brokerage, Telecommunications, Connectivity, and UCaaS.

The CHNLSYNC catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

CHNLSYNC’s developer surface includes changelog, authentication, documentation, getting-started guide, support, and 34 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.6/100 developing Agent 30/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

2 published contracts 1 MCP Servers 2 Agent Skills

CompanyTechnology BrokerageTelecommunications Connectivity UCaaS CCaaS CloudCopper RetirementArtificial Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 50.6/100 · developing

Contract Quality 11.7 / 19

Developer Ergonomics 6.0 / 15

Access Clarity 7.0 / 15

Operational Transparency 2.3 / 10

Contract Governance 2.0 / 9

Discoverability 6.1 / 8

Regulatory Posture 3.6 / 15

Create-or-Update Ergonomics 3.9 / 10

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/chnlsync-com/"><img src="https://apis.io/badge/chnlsync-com/card.svg" alt="CHNLSYNC on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 39.9 — up to +12.0 composite points Ask about this →
Access Clarity scores 46.8 — up to +10.6 composite points Ask about this →
Operational Transparency scores 23.8 — up to +9.9 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/chnlsync-com/apis.yml: open an issue on github.com/api-evangelist/chnlsync-com to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OpenAPI

measured — observed by APIs.io (published)

APIs 12

Individual APIs this provider publishes, each with its own machine-readable definition.

Sync by CHNLSYNC MCP Server

Remote streamable-HTTP MCP server com.chnlsync/advisor (registry version 0.2.0) for FCC copper retirement lookups and a broker-reviewed IT advisor; tools/list returned check_cop...

CHNLSYNC Copper Retirement API

The copper-retirement API from CHNLSYNC — 1 operation(s) for copper-retirement.

CHNLSYNC Customer Agent API

The customer-agent API from CHNLSYNC — 4 operation(s) for customer-agent.

CHNLSYNC Customer API

The customer API from CHNLSYNC — 32 operation(s) for customer.

CHNLSYNC Customer Bills API

The customer-bills API from CHNLSYNC — 7 operation(s) for customer-bills.

CHNLSYNC Customer Decisions API

The customer-decisions API from CHNLSYNC — 2 operation(s) for customer-decisions.

CHNLSYNC Customer Helpdesk API

The customer-helpdesk API from CHNLSYNC — 5 operation(s) for customer-helpdesk.

CHNLSYNC Customer Intake API

The customer-intake API from CHNLSYNC — 4 operation(s) for customer-intake.

CHNLSYNC Customer Inventory API

The customer-inventory API from CHNLSYNC — 8 operation(s) for customer-inventory.

CHNLSYNC Customer Outcomes API

The customer-outcomes API from CHNLSYNC — 1 operation(s) for customer-outcomes.

CHNLSYNC Healthz API

The Healthz API from CHNLSYNC — 1 operation(s) for healthz.

CHNLSYNC Inngest API

The Inngest API from CHNLSYNC — 1 operation(s) for inngest.

Scroll for all 12

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

CHNLSYNC MCP Server

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

check-copper-retirement

AGENT SKILL

consult-advisor

AGENT SKILL

CHNLSYNC API pricing

Prices published by CHNLSYNC.

Plan	Price
Supplier-paid brokerage	CHNLSYNC charges no buyer advisory fee for its supplier-paid brokerage service.

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

CHNLSYNC Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

CHNLSYNC Rate Limits

0 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

CHNLSYNC

7 quoted statements, read from CHNLSYNC's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

CHNLSYNC

12 quoted statements, read from CHNLSYNC's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

CHNLSYNC

2 quoted statements, read from CHNLSYNC's own page on 2026-11-09.

ELIGIBILITY

Data License 1

How its data and outputs may be reused, quoted from its own terms.

CHNLSYNC

1 quoted statement, read from CHNLSYNC's own page on 2026-11-09.

LICENSE

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Chnlsync Com Context

120 classes · 354 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

CHNLSYNC API Rules

52 rules · 37 error-severity 11 warn-severity 4 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

CHNLSYNC Openapi Overlay

6 actions · update · chnlsync-com-openapi.yml

DERIVED

JSON Schema 14

Standalone JSON Schema definitions for this provider's data models.

AgentCallbackRequest

2 properties

JSON SCHEMA

AgentCallbackResponse

3 properties

JSON SCHEMA

AgentChatResponse

6 properties

JSON SCHEMA

AgentSessionCreateRequest

6 properties

JSON SCHEMA

AgentSessionCreateResponse

7 properties

JSON SCHEMA

BillRead

18 properties

JSON SCHEMA

CopperRetirementResponse

6 properties

JSON SCHEMA

CustomerChatResponse

15 properties

JSON SCHEMA

DecisionMutation

24 properties

JSON SCHEMA

RatingInput

3 properties

JSON SCHEMA

RatingResult

1 properties

JSON SCHEMA

ServiceLineInput

15 properties

JSON SCHEMA

ServiceLineUpdate

14 properties

JSON SCHEMA

TicketRead

18 properties

JSON SCHEMA

Scroll for all 14

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

CHNLSYNC Authentication

apiKey/http · 2 schemes

SECURITY

CHNLSYNC Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

CHNLSYNC Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

CHNLSYNC Agentic Access

75 operations · 44 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgentSkill

LLMsTxt

WellKnown

LLMsTxt

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Components

Conventions

Lifecycle

ErrorCatalog

Conformance

Scroll for all 9

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

IntegrationEdges

IntegrationEdges

Access & Security 5

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

Security

Authentication

Authentication

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

Plans

PrivacyPolicy

TermsOfService

UsageTerms

DataLicense

Company 3

The organization behind the API

Website

Website

About

About

LinkedIn

Other 6

Properties that don't map to a standard resource type

Overlay

Hosts

Vendors

Sitemap

DataProcessing

Eligibility

Source (apis.yml)

aid: chnlsync-com
name: CHNLSYNC
description: CHNLSYNC ("The AI-Native Technology Brokerage", tagline "Advise. Source. Manage.") is a technology brokerage
  for businesses with 20-500 employees. Buyers describe what is not working - phone systems at end of life, copper line retirement
  notices, contract renewals, overpriced circuits - and CHNLSYNC builds a case file, researches a network of 300+ suppliers
  and recommends a path across connectivity, UCaaS, CCaaS, CPaaS, security, SASE, cloud, colocation and CX/voice AI, with
  a named human broker (founder Will Kennedy) reviewing every introduction. It uses a supplier-paid model with no buyer advisory
  fee, and publishes a Copper Retirement Tracker with an embeddable widget and JSON feed.
url: https://artifacts.apis.io/chnlsync-com/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-03 (modular-v1; was harvest)
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  probe_state: covered
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-03'
modified: '2026-11-03'
tags:
- Company
- Technology Brokerage
- Telecommunications
- Connectivity
- UCaaS
- CCaaS
- Cloud
- Copper Retirement
- Artificial Intelligence
tags_raw:
- Company
- Technology Brokerage
- Telecommunications
- Connectivity
- UCaaS
- CCaaS
- Cloud
- Copper Retirement
- AI
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
image: https://chnlsync.com/assets/og-image.png
common:
- type: AgenticAccess
  url: agentic-access/chnlsync-com-agentic-access.yml
- type: Plans
  url: plans/chnlsync-com-plans-pricing.yml
- type: Spectral
  url: rules/chnlsync-com-rules.yml
- type: JSONLD
  url: json-ld/chnlsync-com-context.jsonld
- type: Vocabulary
  url: vocabulary/chnlsync-com-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/chnlsync-com-data-model.yml
- type: Components
  url: components/chnlsync-com-components.yml
- type: ChangeLog
  url: changelog/chnlsync-com-changelog.yml
- type: Conventions
  url: conventions/chnlsync-com-conventions.yml
- type: Lifecycle
  url: lifecycle/chnlsync-com-lifecycle.yml
- type: ErrorCatalog
  url: errors/chnlsync-com-problem-types.yml
- type: Conformance
  url: conformance/chnlsync-com-conformance.yml
- type: Overlay
  url: overlays/chnlsync-com-openapi-overlay.yaml
- type: LLMsTxt
  url: llms/chnlsync-com-llms.txt
- type: ToolCrosswalk
  url: mcp/chnlsync-com-tool-crosswalk.yml
- type: SecurityTxt
  url: well-known/chnlsync-com-security.txt
- type: WellKnown
  url: well-known/chnlsync-com-well-known.yml
- type: Hosts
  url: hosts/chnlsync-com-hosts.yml
- type: IntegrationEdges
  url: integrations/chnlsync-com-integration-edges.yml
- type: Vendors
  url: vendors/chnlsync-com-vendors.yml
- type: Security
  url: https://chnlsync.com/solutions/security
- type: Authentication
  url: authentication/chnlsync-com-authentication.yml
- type: VulnerabilityDisclosure
  url: security/chnlsync-com-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/chnlsync-com-domain-security.yml
- type: Website
  url: https://chnlsync.com/
- type: Documentation
  url: https://chnlsync.com/guides/
- type: GettingStarted
  url: https://chnlsync.com/start
- type: About
  url: https://chnlsync.com/about/
- type: PrivacyPolicy
  url: https://chnlsync.com/privacy
- type: TermsOfService
  url: https://chnlsync.com/terms
- type: LinkedIn
  url: https://www.linkedin.com/company/chnlsync
- type: LLMsTxt
  url: https://chnlsync.com/llms.txt
- type: Sitemap
  url: https://chnlsync.com/sitemap.xml
- type: Support
  url: mailto:will@chnlsync.com
- type: UsageTerms
  url: terms/chnlsync-com-terms-of-service.yml
- type: DataProcessing
  url: privacy/chnlsync-com-privacy-policy.yml
- type: Eligibility
  url: eligibility/chnlsync-com-eligibility.yml
- type: DataLicense
  url: data-license/chnlsync-com-data-license.yml
apis:
- aid: chnlsync-com:sync-advisor-mcp
  name: Sync by CHNLSYNC MCP Server
  description: Remote streamable-HTTP MCP server com.chnlsync/advisor (registry version 0.2.0) for FCC copper retirement lookups
    and a broker-reviewed IT advisor; tools/list returned check_copper_retirement, ask_sync_advisor and request_broker_callback.
  humanURL: https://chnlsync.com/
  baseURL: https://mcp.chnlsync.com/mcp
  tags:
  - MCP
  - Copper Retirement
  properties:
  - type: MCPServer
    url: https://mcp.chnlsync.com/mcp
- aid: chnlsync-com:chnlsync-com-copper-retirement-api
  name: CHNLSYNC Copper Retirement API
  description: The copper-retirement API from CHNLSYNC — 1 operation(s) for copper-retirement.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - Copper Retirement
  tags_raw:
  - copper-retirement
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-copper-retirement-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-copper-retirement-response-schema.json
- aid: chnlsync-com:chnlsync-com-customer-agent-api
  name: CHNLSYNC Customer Agent API
  description: The customer-agent API from CHNLSYNC — 4 operation(s) for customer-agent.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-agent
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-agent-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-copper-retirement-response-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-agent-session-create-request-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-agent-session-create-response-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-agent-chat-response-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-agent-callback-response-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-agent-callback-request-schema.json
- aid: chnlsync-com:chnlsync-com-customer-api
  name: CHNLSYNC Customer API
  description: The customer API from CHNLSYNC — 32 operation(s) for customer.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - Customers
  tags_raw:
  - customer
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-customer-chat-response-schema.json
- aid: chnlsync-com:chnlsync-com-customer-bills-api
  name: CHNLSYNC Customer Bills API
  description: The customer-bills API from CHNLSYNC — 7 operation(s) for customer-bills.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-bills
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-bills-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-bill-read-schema.json
- aid: chnlsync-com:chnlsync-com-customer-decisions-api
  name: CHNLSYNC Customer Decisions API
  description: The customer-decisions API from CHNLSYNC — 2 operation(s) for customer-decisions.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-decisions
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-decisions-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-decision-mutation-schema.json
- aid: chnlsync-com:chnlsync-com-customer-helpdesk-api
  name: CHNLSYNC Customer Helpdesk API
  description: The customer-helpdesk API from CHNLSYNC — 5 operation(s) for customer-helpdesk.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-helpdesk
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-helpdesk-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-ticket-read-schema.json
- aid: chnlsync-com:chnlsync-com-customer-intake-api
  name: CHNLSYNC Customer Intake API
  description: The customer-intake API from CHNLSYNC — 4 operation(s) for customer-intake.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-intake
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-intake-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-customer-chat-response-schema.json
- aid: chnlsync-com:chnlsync-com-customer-inventory-api
  name: CHNLSYNC Customer Inventory API
  description: The customer-inventory API from CHNLSYNC — 8 operation(s) for customer-inventory.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - Customer Inventory
  tags_raw:
  - customer-inventory
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-inventory-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-service-line-input-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-service-line-update-schema.json
- aid: chnlsync-com:chnlsync-com-customer-outcomes-api
  name: CHNLSYNC Customer Outcomes API
  description: The customer-outcomes API from CHNLSYNC — 1 operation(s) for customer-outcomes.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - customer-outcomes
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-customer-outcomes-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
  - type: JSONSchema
    url: json-schema/chnlsync-com-rating-input-schema.json
  - type: JSONSchema
    url: json-schema/chnlsync-com-rating-result-schema.json
- aid: chnlsync-com:chnlsync-com-healthz-api
  name: CHNLSYNC Healthz API
  description: The Healthz API from CHNLSYNC — 1 operation(s) for healthz.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - Healthz
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-healthz-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
- aid: chnlsync-com:chnlsync-com-inngest-api
  name: CHNLSYNC Inngest API
  description: The Inngest API from CHNLSYNC — 1 operation(s) for inngest.
  humanURL: https://api.chnlsync.dev/docs
  baseURL: https://api.chnlsync.dev
  tags:
  - Inngest
  properties:
  - type: OpenAPI
    url: openapi/chnlsync-com-inngest-api-openapi.yml
  - type: Documentation
    url: https://api.chnlsync.dev/docs
x-coverage:
  state: covered
  reason: identity-verified
  detail: Name, description, tags and image read from chnlsync.com (title, og meta, llms.txt, /about/). Guides are buyer guides,
    not API docs. app.chnlsync.com returned 404 to a plain GET, so no Login pointer was added.
  evidence:
  - url: https://chnlsync.com/
    status: 200
  - url: https://chnlsync.com/llms.txt
    status: 200
  - url: https://chnlsync.com/about/
    status: 200
  - url: https://chnlsync.com/guides/
    status: 200
  - url: https://chnlsync.com/start
    status: 200
  - url: https://chnlsync.com/privacy
    status: 200
  - url: https://chnlsync.com/terms
    status: 200
  - url: https://chnlsync.com/sitemap.xml
    status: 200
  - url: https://www.linkedin.com/company/chnlsync
    status: 200
  - url: https://chnlsync.com/assets/og-image.png
    status: 200
  - url: https://app.chnlsync.com/
    status: 404
x-enrichment:
  date: '2026-11-03'
  status: enriched
  artifacts_added: 42
  pass: modular-v1
  engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic

CHNLSYNC API — frequently asked questions

Does CHNLSYNC have an API?

Yes. APIs.io lists 12 APIs from CHNLSYNC, including Sync by CHNLSYNC MCP Server, CHNLSYNC Copper Retirement API and CHNLSYNC Customer Agent API, and 9 more.

Is there an OpenAPI specification for the CHNLSYNC API?

Yes. APIs.io indexes 11 OpenAPI specifications for CHNLSYNC, each linked for download from this page.

How do I authenticate with the CHNLSYNC API?

CHNLSYNC uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as CHNLSYNC Authentication.

How much does the CHNLSYNC API cost?

CHNLSYNC publishes its prices; its Supplier-paid brokerage plan is CHNLSYNC charges no buyer advisory fee for its supplier-paid brokerage service. as of 2026-11-03. APIs.io lists 1 pricing plan for CHNLSYNC, with each plan's price, limits and inclusions under Pricing on this page.

Does CHNLSYNC have an MCP server?

Yes. APIs.io lists 1 MCP server for CHNLSYNC.

Is the CHNLSYNC API ready for AI agents?

CHNLSYNC has a Kin Score of 50.6 out of 100 (developing) and an Agent Readiness score of 30.3 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/chnlsync-com"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/chnlsync-com/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/chnlsync-com/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.