Backstory website screenshot

Backstory

Backstory (formerly People.ai, rebranded April 2026) is an AI revenue intelligence platform for sales leaders, CROs, and revenue teams. It automatically captures customer interactions across email, meetings, calls, chat, and CRM records, maps that activity to open deals, and reconstructs what is actually happening inside a deal or account — flagging which deals are losing momentum, where decision-makers are missing, whether a forecast is defensible, and the recommended next step. It integrates with Salesforce, Microsoft Dynamics, Oracle, Gmail, Outlook, Zoom, Teams, Webex, and Slack without requiring reps to change their workflow. Backstory's public developer surface is agent-native rather than REST: it operates a hosted, remote MCP server at https://mcp.people.ai/mcp with thirteen documented tools, protected by OAuth 2.0 with PKCE and dynamic client registration, and documented for Claude, ChatGPT, Microsoft Copilot, Gemini CLI and n8n. A separate REST API exists but is documented only as admin-panel API key management, with no published reference or specification. Backstory is backed by ICONIQ Capital, Andreessen Horowitz, and Lightspeed Venture Partners.

Backstory publishes 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Revenue Intelligence, Sales, and CRM.

Backstory’s developer surface includes engineering blog, pricing, support, documentation, getting-started guide, changelog, authentication, and 25 more developer resources.

33.5/100 thin ▬ flat Agent 29/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs 1 MCP Servers
CompanyArtificial IntelligenceRevenue IntelligenceSalesCRMSales AnalyticsForecastingRevenue OperationsMCPAI Agents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
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 github.com/api-evangelist/backstory: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Backstory MCP

Backstory's hosted, remote Model Context Protocol server. It lets an AI client query a customer's own Backstory revenue-intelligence data — accounts, opportunities, recent activ...

MCP Servers 1

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

Backstory MCP

Backstory MCP is the provider's hosted, remote Model Context Protocol server. It lets AI clients (Claude, ChatGPT, Microsoft Copilot, Google Gemini CLI, n8n AI Agent nodes, or a...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Backstory Rate Limits

0 limits

RATE LIMITS

Security Posture 3

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

Backstory Authentication

oauth2/apiKey/http · 4 schemes

SECURITY

Backstory Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Backstory Trust Center

SOC 2, ISO 27001, ISO 27017, GDPR, CSA STAR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Backstory Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: backstory
name: Backstory
description: 'Backstory (formerly People.ai, rebranded April 2026) is an AI revenue intelligence platform for sales leaders,
  CROs, and revenue teams. It automatically captures customer interactions across email, meetings, calls, chat, and CRM records,
  maps that activity to open deals, and reconstructs what is actually happening inside a deal or account — flagging which
  deals are losing momentum, where decision-makers are missing, whether a forecast is defensible, and the recommended next
  step. It integrates with Salesforce, Microsoft Dynamics, Oracle, Gmail, Outlook, Zoom, Teams, Webex, and Slack without requiring
  reps to change their workflow. Backstory''s public developer surface is agent-native rather than REST: it operates a hosted,
  remote MCP server at https://mcp.people.ai/mcp with thirteen documented tools, protected by OAuth 2.0 with PKCE and dynamic
  client registration, and documented for Claude, ChatGPT, Microsoft Copilot, Gemini CLI and n8n. A separate REST API exists
  but is documented only as admin-panel API key management, with no published reference or specification. Backstory is backed
  by ICONIQ Capital, Andreessen Horowitz, and Lightspeed Venture Partners.'
url: https://raw.githubusercontent.com/api-evangelist/backstory/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- iconiq-capital
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-14'
image: https://cdn.prod.website-files.com/69aab19e3344fee750b8721c/69bc218831a2d8ce7c69e9da_ab2eb85cd7fb357375e2a489f3bb519f_Backstory_OG.jpg
tags:
- Company
- Artificial Intelligence
- Revenue Intelligence
- Sales
- CRM
- Sales Analytics
- Forecasting
- Revenue Operations
- MCP
- AI Agents
tags_raw:
- Company
- Ai
- Revenue Intelligence
- Sales
- CRM
- Sales Analytics
- Forecasting
- Revenue Operations
- MCP
- AI Agents
apis:
- name: Backstory MCP
  description: 'Backstory''s hosted, remote Model Context Protocol server. It lets an AI client query a customer''s own Backstory
    revenue-intelligence data — accounts, opportunities, recent activity, engaged people, scorecards, company news, and SalesAI
    analysis — in natural language. Thirteen tools are published across four families: finding accounts and opportunities,
    strategic summaries, activity and engagement review, and advanced sales analysis (including a beta Situation Search that
    returns historically similar deals with the actions taken and the outcome). Authorization is OAuth 2.0 authorization_code
    with PKCE and dynamic client registration; a connected client inherits exactly the record permissions the authenticating
    user already has in Backstory Engagement Dashboards and gains nothing more.'
  humanURL: https://www.backstory.ai/platform/mcp
  baseURL: https://mcp.people.ai/mcp
  tags:
  - MCP
  - AI Agents
  - Revenue Intelligence
  - CRM
  properties:
  - type: MCPServer
    url: mcp/backstory-mcp.yml
  - type: Documentation
    url: https://help.backstory.ai/en/articles/15252736-backstory-mcp
  - type: GettingStarted
    url: https://help.backstory.ai/en/collections/19658946-mcp
  - type: Authentication
    url: authentication/backstory-authentication.yml
  - type: OAuthScopes
    url: scopes/backstory-scopes.yml
  - type: ErrorCatalog
    url: errors/backstory-problem-types.yml
  - type: Conventions
    url: conventions/backstory-conventions.yml
  - type: RateLimits
    url: rate-limits/backstory-rate-limits.yml
  - type: AgentSkill
    url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.backstory.ai/
- type: Blog
  url: https://www.backstory.ai/newsroom
- type: Login
  url: https://app.people.ai/login/
- type: PrivacyPolicy
  url: https://www.backstory.ai/privacy
- type: TermsOfService
  url: https://www.backstory.ai/terms
- type: Pricing
  url: https://www.backstory.ai/pricing
- type: Support
  url: mailto:support@backstory.ai
- type: HelpCenter
  url: https://help.backstory.ai/en/
- type: Documentation
  url: https://help.backstory.ai/en/
- type: GettingStarted
  url: https://help.backstory.ai/en/collections/19646748-get-started
- type: GitHubOrganization
  url: https://github.com/people-ai
- type: TrustCenter
  url: https://www.backstory.ai/platform/trust-security
- type: Compliance
  url: https://www.backstory.ai/platform/trust-security
- type: StatusPage
  url: https://status.backstory.ai/
- type: ChangeLog
  url: https://help.backstory.ai/en/articles/15252920-new-product-releases
- type: ChangeLog
  url: changelog/backstory-changelog.yml
- type: Lifecycle
  url: lifecycle/backstory-lifecycle.yml
- type: MCPServer
  url: mcp/backstory-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/backstory-authentication.yml
- type: OAuthScopes
  url: scopes/backstory-scopes.yml
- type: Conventions
  url: conventions/backstory-conventions.yml
- type: ErrorCatalog
  url: errors/backstory-problem-types.yml
- type: Conformance
  url: conformance/backstory-conformance.yml
- type: WellKnown
  url: well-known/backstory-well-known.yml
- type: Packages
  url: packages/backstory-packages.yml
- type: Components
  url: components/backstory-components.yml
- type: Plans
  url: plans/backstory-plans-pricing.yml
- type: RateLimits
  url: rate-limits/backstory-rate-limits.yml
- type: LLMsTxt
  url: llms/backstory-llms.txt
- type: LLMsTxt
  url: llms/backstory-help-llms.txt
- type: DomainSecurity
  url: security/backstory-domain-security.yml
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 15
  pass: local-v1

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/backstory"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/backstory/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/backstory/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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