Endgame

Endgame (Endgame Labs, Inc.) is a context graph platform for go-to-market teams and AI agents that turns sales calls, CRM records, emails, Slack conversations, meeting transcripts, and uploaded documents into structured, queryable revenue intelligence. Sales and RevOps users ask questions across their book of business in natural language, and connected AI assistants reach the same knowledge through the Endgame MCP Server. The public REST API (rooted at /api/v1) lets developers create and manage Endgame threads programmatically over HTTPS with Bearer-token authentication, while a broad connector surface ingests context from Salesforce, Gong, Chorus, Clari Copilot, Zoom, Notion, Confluence, Highspot, Seismic, Snowflake, Slack, Microsoft Teams/SharePoint/Outlook, and Google Drive. Endgame was surfaced through the API Evangelist VC-portfolio pipeline and has been enriched from its published developer documentation, OpenAPI, MCP server, and trust/security programs.

Endgame publishes 3 API contracts indexed on the APIs.io network: Threads API, Internal API, and Protected Static API. Tagged areas include Company, Sales, Revenue Intelligence, Go-To-Market, and Artificial Intelligence.

The Endgame catalog on APIs.io includes 1 Spectral governance ruleset.

Endgame’s developer surface includes authentication, documentation, API reference, getting-started guide, changelog, support, engineering blog, and 39 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

59.2/100 strong ▬ flat Agent 50/100 agent ready Front door AI 5/6 prominent Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 1 MCP Servers 3 Agent Skills

Company Sales Revenue Intelligence Go-To-Market Artificial Intelligence Agents MCP Knowledge Graph CRM Conversation Intelligence A2A

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 59.2/100 · strong

Contract Quality 8.8 / 19

Developer Ergonomics 10.7 / 15

Access Clarity 7.5 / 15

Operational Transparency 6.4 / 10

Contract Governance 2.9 / 9

Discoverability 5.6 / 8

Regulatory Posture 6.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 50/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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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/end-game/"><img src="https://apis.io/badge/end-game/card.svg" alt="Endgame 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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's

4 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 46.9 — up to +13.3 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

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.

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/end-game/apis.yml: open an issue on github.com/api-evangelist/end-game 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 7

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.

Agent2Agent

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

Agent Skills

measured — observed by APIs.io (published)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 3

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

Endgame Threads API

The public Threads API from Endgame — 5 operations (create, get, list, rename, delete) rooted at /api/v1 on https://app.endgame.io, authenticated with a Bearer eak_ API key or a...

Endgame Internal API

The Internal API from Endgame — 3 operation(s) for internal.

Endgame Protected Static API

The Protected Static API from Endgame — 2 operation(s) for protected static.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Endgame Public Threads API

OPEN COLLECTION

MCP Servers 1

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

Endgame MCP Server

Remote MCP server at app.endgame.io over HTTP requiring OAuth; 4 tools listed.

MCP SERVER

Agent Skills 3

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

Ask Endgame a revenue question

AGENT SKILL

List, rename, and delete Endgame threads

AGENT SKILL

Endgame

AGENT SKILL

Endgame API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

End Game Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

End Game Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

End Game Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Endgame API Rules

45 rules · 43 errors 1 warnings 1 info

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.

End Game Openapi Overlay

3 actions · update · end-game-openapi.json

DERIVED

Security Posture 4

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

End Game Authentication

http/oauth2 · 2 schemes

SECURITY

End Game Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

End Game Vulnerability Disclosure

contact published

SECURITY

End Game Trust Center

SOC 2, ISO 27001

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

End Game Scopes

4 scopes

SCOPES

Agentic Access 1

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

End Game Agentic Access

17 operations · 10 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Agent Surfaces 7

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

MCPServer

LLMsTxt

AgentSkill

AgentSkill

WellKnown

LLMsTxt

Scroll for all 7

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Conformance

Lifecycle

Build 5

SDKs, sample code, and the tooling you integrate with

Packages

Packages

CLI

CLI

ToolCrosswalk

ToolCrosswalk

GitHubOrganization

GitHubOrganization

SourceCode

SourceCode

Access & Security 9

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

Authentication

Authentication

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

OAuthScopes

OAuthScopes

TrustCenter

TrustCenter

Scroll for all 9

Operate 6

Status, limits, changes, and where to get help

ChangeLog

StatusPage

Support

RateLimits

ChangeLog

Contact

Commercial 4

Pricing, plans, and the legal terms of use

License

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

AgentCard

AgentCard

Source (apis.yml)

aid: end-game
name: Endgame
description: Endgame (Endgame Labs, Inc.) is a context graph platform for go-to-market teams and AI agents that turns sales
  calls, CRM records, emails, Slack conversations, meeting transcripts, and uploaded documents into structured, queryable
  revenue intelligence. Sales and RevOps users ask questions across their book of business in natural language, and connected
  AI assistants reach the same knowledge through the Endgame MCP Server. The public REST API (rooted at /api/v1) lets developers
  create and manage Endgame threads programmatically over HTTPS with Bearer-token authentication, while a broad connector
  surface ingests context from Salesforce, Gong, Chorus, Clari Copilot, Zoom, Notion, Confluence, Highspot, Seismic, Snowflake,
  Slack, Microsoft Teams/SharePoint/Outlook, and Google Drive. Endgame was surfaced through the API Evangelist VC-portfolio
  pipeline and has been enriched from its published developer documentation, OpenAPI, MCP server, and trust/security programs.
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: true
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - pricing
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.endgame.io/opengraph-image
url: https://raw.githubusercontent.com/api-evangelist/end-game/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
x-tier: profiled
x-tier-reason: enriched-from-developer-docs
x-legal-entity: Endgame Labs, Inc.
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
tags:
- Company
- Sales
- Revenue Intelligence
- Go-To-Market
- Artificial Intelligence
- Agents
- MCP
- Knowledge Graph
- CRM
- Conversation Intelligence
- A2A
apis:
- aid: end-game:end-game-threads-api
  name: Endgame Threads API
  description: 'The public Threads API from Endgame — 5 operations (create, get, list, rename, delete) rooted at /api/v1 on
    https://app.endgame.io, authenticated with a Bearer eak_ API key or a WorkOS M2M access token. Threads are the conversational
    unit behind Endgame Chat: POST a natural-language prompt, then poll the thread until the assistant''s asynchronous response
    reaches status.state idle or error.'
  humanURL: https://docs.endgame.io/api-reference/introduction
  baseURL: https://app.endgame.io
  tags:
  - Threads
  properties:
  - type: OpenAPI
    url: openapi/end-game-threads-api-openapi.yml
  - type: OpenAPI
    name: Endgame Public API (spec served live at /api/v1/openapi.json)
    url: openapi/_original/end-game-public-api-served-openapi.json
  - type: Documentation
    url: https://docs.endgame.io/api-reference/introduction
  - type: APIReference
    url: https://docs.endgame.io/api-reference/endpoints
  - type: Authentication
    url: https://docs.endgame.io/api-reference/authentication
- aid: end-game:end-game-internal-api
  name: Endgame Internal API
  description: The Internal API from Endgame — 3 operation(s) for internal.
  humanURL: https://docs.endgame.io/api-reference/introduction
  baseURL: https://app.endgame.io
  tags:
  - Internal
  properties:
  - type: OpenAPI
    url: openapi/end-game-internal-api-openapi.yml
- aid: end-game:end-game-protected-static-api
  name: Endgame Protected Static API
  description: The Protected Static API from Endgame — 2 operation(s) for protected static.
  humanURL: https://docs.endgame.io/api-reference/introduction
  baseURL: https://app.endgame.io
  tags:
  - Protected Static
  properties:
  - type: OpenAPI
    url: openapi/end-game-protected-static-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: License
  name: MIT
  url: https://github.com/Endgame-Labs/endgame-cli/blob/main/LICENSE
- type: TrustCenter
  url: security/end-game-trust-center.yml
- type: DomainSecurity
  url: security/end-game-domain-security.yml
- type: AgenticAccess
  url: agentic-access/end-game-agentic-access.yml
- type: Authentication
  url: authentication/end-game-authentication.yml
- type: Website
  url: https://www.endgame.io
- type: DeveloperPortal
  url: https://docs.endgame.io
- type: Documentation
  url: https://docs.endgame.io
- type: APIReference
  url: https://docs.endgame.io/api-reference/endpoints
- type: GettingStarted
  url: https://docs.endgame.io/api-reference/introduction
- type: Authentication
  url: https://docs.endgame.io/api-reference/authentication
- type: MCPServer
  url: mcp/end-game-mcp.yml
- type: OpenAPI
  url: openapi/_original/end-game-openapi.json
- type: LLMsTxt
  url: llms/end-game-llms.txt
- type: ChangeLog
  url: https://docs.endgame.io/changelog
- type: StatusPage
  url: https://status.endgame.io
- type: Support
  url: https://docs.endgame.io/contact
- type: Blog
  url: https://www.endgame.io/blog
- type: SignUp
  url: https://www.endgame.io/signup
- type: TermsOfService
  url: https://www.endgame.io/terms
- type: PrivacyPolicy
  url: https://docs.endgame.io/trust/privacy
- type: Compliance
  url: https://docs.endgame.io/trust/security
- type: VulnerabilityDisclosure
  url: https://docs.endgame.io/vdp
- type: Security
  url: https://docs.endgame.io/vdp
- type: ErrorCatalog
  url: errors/end-game-error-codes.yml
- type: Conventions
  url: conventions/end-game-conventions.yml
- type: DataModel
  url: data-model/end-game-data-model.yml
- type: RateLimits
  url: rate-limits/end-game-rate-limits.yml
- type: Conformance
  url: conformance/end-game-conformance.yml
- type: Lifecycle
  url: lifecycle/end-game-lifecycle.yml
- type: Overlay
  url: overlays/end-game-openapi-overlay.yaml
- type: ChangeLog
  url: changelog/end-game-changelog.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgentSkill
  name: Endgame (provider-published Agent Skill)
  url: skills/end-game-published-skill.md
- type: AgentCard
  url: a2a/end-game-a2a.yml
- type: WellKnown
  url: well-known/end-game-well-known.yml
- type: OAuthScopes
  url: scopes/end-game-scopes.yml
- type: Packages
  url: packages/end-game-packages.yml
- type: CLI
  url: cli/end-game-cli.yml
- type: ToolCrosswalk
  url: mcp/end-game-tool-crosswalk.yml
- type: Plans
  url: plans/end-game-plans-pricing.yml
- type: GitHubOrganization
  url: https://github.com/Endgame-Labs
- type: SourceCode
  name: Endgame CLI
  url: https://github.com/Endgame-Labs/endgame-cli
- type: TrustCenter
  name: Endgame trust center (Drata)
  url: https://app.drata.com/trust/9cbf820f-0c38-11ee-865f-029d78a187d9
- type: LLMsTxt
  name: Endgame website llms.txt
  url: llms/end-game-website-llms.txt
- type: Contact
  url: mailto:support@endgame.io
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 13
  pass: local-v1
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://docs.endgame.io/.well-known/agent-card.json
  grade: conformant
  protocol_version: '0.3'
  control: 404

Endgame API — frequently asked questions

Does Endgame have an API?

Yes. APIs.io lists 3 APIs from Endgame, including Endgame Threads API, Endgame Internal API and Endgame Protected Static API.

Is there an OpenAPI specification for the Endgame API?

Yes. APIs.io indexes 3 OpenAPI specifications for Endgame, each linked for download from this page.

How do I authenticate with the Endgame API?

Endgame documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as End Game Authentication.

Does Endgame have an MCP server?

Yes. APIs.io lists 1 MCP server for Endgame: Remote MCP server at app.endgame.io over HTTP requiring OAuth; 4 tools listed.

Is the Endgame API ready for AI agents?

Endgame has a Kin Score of 59.2 out of 100 (strong) and an Agent Readiness score of 49.7 (agent-ready), scored by API Evangelist on 2026-11-06.

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/end-game"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/end-game/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.