COR
COR (COR Global Ltd., projectcor.com) is an AI-powered management platform for advertising and creative agencies that calculates and forecasts project profitability while managing finances, resources, projects, tasks, and time tracking in one real-time workspace. COR publishes a REST API (JSON or XML) for projects, tasks, hours, clients, contracts, transactions, teams, users, and more, a separate Resource Allocation API, and an official hosted MCP server so AI clients can operate a workspace with natural language. Backed by 500 Global.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles COR the way a machine reads it — 58 machine-readable artifacts across 2 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 — COR scores 37.0/100 (thin), with a separate agent-readiness read of 33/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from COR's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cor/"
title="COR on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cor.svg"
alt="COR Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/cor/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cor/"
title="COR on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cor/card.svg"
alt="COR Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile COR
Each block below is one kind of artifact we hold for COR. 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 27
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.
COR Attachments API
The Attachments API from COR — 1 operation(s) for attachments.
COR Auth API
The Auth API from COR — 5 operation(s) for auth.
COR Brands API
The Brands API from COR — 2 operation(s) for brands.
COR Clients API
The Clients API from COR — 4 operation(s) for clients.
COR Collaborators API
The Collaborators API from COR — 2 operation(s) for collaborators.
COR Contacts API
The Contacts API from COR — 3 operation(s) for contacts.
COR Contract Positions API
The Contract Positions API from COR — 2 operation(s) for contract positions.
COR Contracts API
The Contracts API from COR — 2 operation(s) for contracts.
COR Contracts Users API
The Contracts Users API from COR — 1 operation(s) for contracts users.
COR Costs API
The Costs API from COR — 2 operation(s) for costs.
COR Estimates API
The Estimates API from COR — 2 operation(s) for estimates.
COR Fees API
The Fees API from COR — 4 operation(s) for fees.
COR Hours API
The Hours API from COR — 6 operation(s) for hours.
COR Labels API
The Labels API from COR — 2 operation(s) for labels.
COR Messages API
The Messages API from COR — 2 operation(s) for messages.
COR Products API
The Products API from COR — 2 operation(s) for products.
COR Project Templates API
The Project Templates API from COR — 1 operation(s) for project templates.
COR Projects API
The Projects API from COR — 14 operation(s) for projects.
COR Ratecards API
The Ratecards API from COR — 3 operation(s) for ratecards.
COR Resource Allocation API
The Resource Allocation API from COR — 4 operation(s) for resource allocation.
COR Tasks API
The Tasks API from COR — 8 operation(s) for tasks.
COR Teams API
The Teams API from COR — 3 operation(s) for teams.
COR Transactions API
The Transactions API from COR — 6 operation(s) for transactions.
COR User Leaves API
The User Leaves API from COR — 4 operation(s) for user leaves.
COR User Positions API
The User Positions API from COR — 4 operation(s) for user positions.
COR Users API
The Users API from COR — 4 operation(s) for users.
COR Working Time API
The Working Time API from COR — 2 operation(s) for working time.
Scroll within the panel for all 27 ·
Open Collections 28
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCOR Attachments API
OPEN COLLECTIONCOR Attachments Auth API
OPEN COLLECTIONCOR Attachments Brands API
OPEN COLLECTIONCOR Attachments Clients API
OPEN COLLECTIONCOR Attachments Collaborators API
OPEN COLLECTIONCOR Attachments Contacts API
OPEN COLLECTIONCOR Attachments Contract Positions API
OPEN COLLECTIONCOR Attachments Contracts API
OPEN COLLECTIONCOR Attachments Contracts Users API
OPEN COLLECTIONCOR Attachments Costs API
OPEN COLLECTIONCOR Attachments Estimates API
OPEN COLLECTIONCOR Attachments Fees API
OPEN COLLECTIONCOR Attachments Hours API
OPEN COLLECTIONCOR Attachments Labels API
OPEN COLLECTIONCOR Attachments Messages API
OPEN COLLECTIONCOR Attachments Products API
OPEN COLLECTIONCOR Attachments Project Templates API
OPEN COLLECTIONCOR Attachments Projects API
OPEN COLLECTIONCOR Attachments Ratecards API
OPEN COLLECTIONCOR Attachments Resource Allocation API
OPEN COLLECTIONCOR Attachments Tasks API
OPEN COLLECTIONCOR Attachments Teams API
OPEN COLLECTIONCOR Attachments Transactions API
OPEN COLLECTIONCOR Attachments User Leaves API
OPEN COLLECTIONCOR Attachments User Positions API
OPEN COLLECTIONCOR Attachments Users API
OPEN COLLECTIONCOR Attachments Working Time API
OPEN COLLECTIONScroll 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.
COR MCP Server
Official hosted Model Context Protocol server that connects any MCP-compatible AI client to a COR workspace using natural language.
MCP SERVERSecurity 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.
Resources
Every other property we hold for COR — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cor · machine-readable index on apis.io
This is an independent, third-party profile of COR, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.