Coperniq
Coperniq is an AI-powered operating system for residential and commercial contractors across solar, storage, HVAC, electrical, plumbing, and roofing trades, consolidating sales, project management, service operations, dispatch, and cashflow into one system. Its REST API (https://api.coperniq.io/v1) lets developers automate projects, opportunities, accounts, contacts, sites, assets, work orders, forms, quotes, invoices, bills, payments, and more, with API-key authentication, page-based pagination, per-key rate limiting, and outbound automation webhooks. Coperniq was surfaced as a portfolio company of Initialized Capital (sector: climate) and enriched into the API Evangelist network from its public developer surface.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Coperniq the way a machine reads it — 34 machine-readable artifacts across 28 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Coperniq scores 57.5/100 (developing), with a separate agent-readiness read of 82/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Coperniq
Each block below is one kind of artifact we hold for Coperniq. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Coperniq accounts API
The accounts API from Coperniq — 3 operation(s) for accounts.
Coperniq ahJs API
The ahJs API from Coperniq — 2 operation(s) for ahjs.
Coperniq appointments API
The appointments API from Coperniq — 2 operation(s) for appointments.
Coperniq assets API
The assets API from Coperniq — 2 operation(s) for assets.
Coperniq authentication API
The authentication API from Coperniq — 1 operation(s) for authentication.
Coperniq bills API
The bills API from Coperniq — 3 operation(s) for bills.
Coperniq calls API
The calls API from Coperniq — 3 operation(s) for calls.
Coperniq catalogItems API
The catalogItems API from Coperniq — 2 operation(s) for catalogitems.
Coperniq contacts API
The contacts API from Coperniq — 2 operation(s) for contacts.
Coperniq files API
The files API from Coperniq — 6 operation(s) for files.
Coperniq forms API
The forms API from Coperniq — 4 operation(s) for forms.
Coperniq formTemplates API
The formTemplates API from Coperniq — 2 operation(s) for formtemplates.
Coperniq invoices API
The invoices API from Coperniq — 4 operation(s) for invoices.
Coperniq labels API
The labels API from Coperniq — 2 operation(s) for labels.
Coperniq lineItems API
The lineItems API from Coperniq — 2 operation(s) for lineitems.
Coperniq notes API
The notes API from Coperniq — 5 operation(s) for notes.
Coperniq opportunities API
The opportunities API from Coperniq — 3 operation(s) for opportunities.
Coperniq payments API
The payments API from Coperniq — 4 operation(s) for payments.
Coperniq projects API
The projects API from Coperniq — 3 operation(s) for projects.
Coperniq properties API
The properties API from Coperniq — 1 operation(s) for properties.
Coperniq quotes API
The quotes API from Coperniq — 5 operation(s) for quotes.
Coperniq reminders API
The reminders API from Coperniq — 4 operation(s) for reminders.
Coperniq sites API
The sites API from Coperniq — 3 operation(s) for sites.
Coperniq taxes API
The taxes API from Coperniq — 1 operation(s) for taxes.
Coperniq users API
The users API from Coperniq — 3 operation(s) for users.
Coperniq vendors API
The vendors API from Coperniq — 4 operation(s) for vendors.
Coperniq workflows API
The workflows API from Coperniq — 2 operation(s) for workflows.
Coperniq workOrders API
The workOrders API from Coperniq — 9 operation(s) for workorders.
Scroll within the panel for all 28 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
coperniq-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Coperniq Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Coperniq Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Coperniq — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/coperniq · machine-readable index on apis.io