Orum is an AI-powered sales calling and performance platform, marketed as "The Calling Performance System for Sales Teams" and "the AI-powered Live Conversation Platform to supercharge sales activity, connect teams, and drive more revenue." Its products are a parallel Dialer (up to 5 lines on the Launch plan, 10 on Ascend), Salesfloor for virtual co-selling, a Coaching and Enablement suite, Orum AI trained on a claimed one billion-plus sales calls, and Scout, a set of AI data agents. It positions itself as purpose-built for maximizing live conversations and explicitly distinct from the dialers built into CRMs and sales-engagement platforms, integrating instead with Salesforce, HubSpot, Outreach, Salesloft, Gong Engage and Apollo. Pricing is two named plans, Launch and Ascend, both contact-sales with a three-seat minimum and no published figures, plus a free trial capped at 500 dials; AI Coaching and Webhooks are paid add-ons. Orum publishes NO request API — no OpenAPI, no API reference, no developer portal, no SDKs, no CLI, no MCP server, no llms.txt, and api./docs./developers.orum.com do not resolve. Its one machine-facing contract is an outbound webhook, and contrary to the first profiling pass it IS publicly documented: a help-center article publishes the single `call-disposition-added` event, the `{event, payload, test}` envelope, HMAC-SHA256 signature verification over an `x-webhook-signature` header, a 15-second ack timeout, an 8-attempt/30-minute exponential-backoff retry policy and three egress IPs. The article is simply unlinked from any directory and reachable only from the 2025-04-14 launch blog post. Orum also publishes a dated product-update feed, a status page, a trust portal, a responsible-disclosure policy, Auth0-backed SSO (SAML/OIDC/OAuth 2.0), a Chrome extension, and SOC 2 Type 2 plus ISO 27001:2022, 27017:2015, 27018:2019 and 27701:2019 attestations.
Orum is profiled on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Sales, Sales Engagement, and Sales Dialer.
The Orum catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Orum’s developer surface includes authentication, changelog, sandbox, documentation, getting-started guide, pricing, support, and 31 more developer resources.
49.4/100developing▬ flatAgent22/100agent awareFront door AI5/6
prominent
Heartbeat19/100
slowing
saas
Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
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 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.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% 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/orum-com/"><img src="https://apis.io/badge/orum-com/card.svg" alt="Orum 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):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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
9 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
aid: orum-com
name: Orum
description: 'Orum is an AI-powered sales calling and performance platform, marketed as "The Calling Performance System for
Sales Teams" and "the AI-powered Live Conversation Platform to supercharge sales activity, connect teams, and drive more
revenue." Its products are a parallel Dialer (up to 5 lines on the Launch plan, 10 on Ascend), Salesfloor for virtual co-selling,
a Coaching and Enablement suite, Orum AI trained on a claimed one billion-plus sales calls, and Scout, a set of AI data
agents. It positions itself as purpose-built for maximizing live conversations and explicitly distinct from the dialers
built into CRMs and sales-engagement platforms, integrating instead with Salesforce, HubSpot, Outreach, Salesloft, Gong
Engage and Apollo. Pricing is two named plans, Launch and Ascend, both contact-sales with a three-seat minimum and no published
figures, plus a free trial capped at 500 dials; AI Coaching and Webhooks are paid add-ons. Orum publishes NO request API
— no OpenAPI, no API reference, no developer portal, no SDKs, no CLI, no MCP server, no llms.txt, and api./docs./developers.orum.com
do not resolve. Its one machine-facing contract is an outbound webhook, and contrary to the first profiling pass it IS publicly
documented: a help-center article publishes the single `call-disposition-added` event, the `{event, payload, test}` envelope,
HMAC-SHA256 signature verification over an `x-webhook-signature` header, a 15-second ack timeout, an 8-attempt/30-minute
exponential-backoff retry policy and three egress IPs. The article is simply unlinked from any directory and reachable only
from the 2025-04-14 launch blog post. Orum also publishes a dated product-update feed, a status page, a trust portal, a
responsible-disclosure policy, Auth0-backed SSO (SAML/OIDC/OAuth 2.0), a Chrome extension, and SOC 2 Type 2 plus ISO 27001:2022,
27017:2015, 27018:2019 and 27701:2019 attestations.'
url: https://raw.githubusercontent.com/api-evangelist/orum-com/refs/heads/main/apis.yml
x-type: company
x-source: conversation:graph8
x-tier: stub
x-tier-reason: conversation-lead
x-disambiguation: Slugged `orum-com` for orum.com, the AI sales dialer. NOT to be confused with `all/orum`, which is orum.io
— an unrelated payments-infrastructure company (FedNow/RTP/ACH money movement and bank-account verification). Two different
companies, near-identical names, same product-adjacent buyer. `all/orum` keeps its bare slug because it is already referenced
by four published paper bundles and ~25k generated pages; per the domain-slug convention the TLD is appended only where
needed to disambiguate, which is here.
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: sales-led
trial: true
try_now: false
public: false
label: Contact sales, 3-seat minimum, 500-dial free trial
confidence: high
source:
- https://www.orum.com/pricing
generated: '2026-08-04'
method: searched
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-13'
image: https://cdn.sanity.io/images/w0eqmudi/production/2b821b473a58f9c3510eb28647c02e861d32727c-2000x1050.heif
tags:
- Company
- Artificial Intelligence
- Sales
- Sales Engagement
- Sales Dialer
- Outbound Sales
- Sales Coaching
- Conversation Intelligence
- Telephony
- Revenue Operations
- Webhook
- Parallel Dialing
- Sales Automation
tags_raw:
- Company
- AI
- Sales
- Sales Engagement
- Sales Dialer
- Outbound Sales
- Sales Coaching
- Conversation Intelligence
- Telephony
- Revenue Operations
- Webhooks
- Parallel Dialing
- Sales Automation
apis: []
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: TrustCenter
url: security/orum-com-trust-center.yml
- type: DomainSecurity
url: security/orum-com-domain-security.yml
- type: Webhooks
url: asyncapi/orum-com-webhooks.yml
- type: Authentication
url: authentication/orum-com-authentication.yml
- type: Conventions
url: conventions/orum-com-conventions.yml
- type: ChangeLog
url: changelog/orum-com-changelog.yml
- type: ChangeLog
url: https://www.orum.com/product-updates
- type: Lifecycle
url: lifecycle/orum-com-lifecycle.yml
- type: VulnerabilityDisclosure
url: security/orum-com-vulnerability-disclosure.yml
- type: Conformance
url: conformance/orum-com-conformance.yml
- type: Plans
url: plans/orum-com-plans-pricing.yml
- type: RateLimits
url: rate-limits/orum-com-rate-limits.yml
- type: Sandbox
url: sandbox/orum-com-sandbox.yml
- type: Packages
url: packages/orum-com-packages.yml
- type: Components
url: components/orum-com-components.yml
- type: LLMsTxt
url: llms/orum-com-llms.txt
- type: GitHubOrganization
url: https://github.com/orumhq
- type: Documentation
url: https://support.orum.com/en-US/orum/directories
- type: GettingStarted
url: https://support.orum.com/en-US/orum/directories/4XGqC47h
- type: Website
url: https://www.orum.com/
- type: Pricing
url: https://www.orum.com/pricing
- type: Support
url: https://support.orum.com/en-US/orum
- type: Blog
url: https://www.orum.com/blog
- type: StatusPage
url: https://status.orum.com
- type: TrustCenter
url: https://trust.orum.com
- type: Compliance
url: https://www.orum.com/platform/security
- type: Security
url: https://www.orum.com/responsible_disclosure
- type: TermsOfService
url: https://www.orum.com/terms
- type: PrivacyPolicy
url: https://www.orum.com/privacy
- type: DataProcessingAddendum
url: https://www.orum.com/data_processing_addendum
- type: TechnicalAndOrganizationalMeasures
url: https://www.orum.com/platform/security/technical-and-organizational-measures
- type: Integrations
url: https://www.orum.com/platform/integrations
- type: Partners
url: https://www.orum.com/partners
- type: CaseStudies
url: https://www.orum.com/customer-stories
- type: Reports
url: https://www.orum.com/reports-and-guides
- type: Podcast
url: https://www.orum.com/podcasts
- type: Demo
url: https://www.orum.com/request-demo
- type: About
url: https://www.orum.com/about
- type: Careers
url: https://www.orum.com/careers
x-evidence:
harvested: '2026-08-04'
request: Surfaced by the graph8 / Thomas Cornelius call 2026-08-04, where Orum was named as a power-dialer competitor. Catalog
held only orum.io under the `orum` slug, so the dialer was entirely absent.
probes:
- https://www.orum.com/ -> HTTP 200 (orum.com redirects to www)
- https://orum.com/llms.txt -> HTTP 404
- https://orum.com/openapi.json -> HTTP 404
- https://orum.com/.well-known/api-catalog -> HTTP 404
- https://orum.com/mcp -> HTTP 404
- https://orum.com/developers -> HTTP 404
- https://orum.com/api -> HTTP 404
- https://docs.orum.com -> DNS does not resolve (curl 000)
- https://developers.orum.com -> DNS does not resolve (curl 000)
- https://api.orum.com/openapi.json -> DNS does not resolve (curl 000)
- https://app.orum.com -> DNS does not resolve (curl 000)
- https://status.orum.com -> HTTP 200, components Dialer / Salesfloor / Analytics / Coaching suite, third-party Vonage Voice
API + HubSpot API
- https://trust.orum.com -> HTTP 200
- https://support.orum.com/en-US/orum -> HTTP 200, help center only, no API articles found
- https://www.orum.com/pricing -> HTTP 200, Launch + Ascend, contact-sales, 3-seat minimum
- https://www.orum.com/platform/security -> HTTP 200, SOC 2 Type 2 + ISO 27001/27017/27018/27701
- https://www.orum.com/{blog,about,careers,terms,privacy,responsible_disclosure} -> HTTP 200
- https://www.orum.com/{data_processing_addendum,partners,customer-stories} -> HTTP 200
- https://www.orum.com/{podcasts,reports-and-guides,platform/integrations} -> HTTP 200
- https://github.com/orumcom -> HTTP 404 (no GitHub org found)
- https://www.orum.com/software_and_services_agreement -> HTTP 404 (linked in footer, dead)
- https://www.orum.com/oauth -> HTTP 404 (linked in nav as "Sign in", dead to a plain GET)
findings:
no_public_api: 'No request API. No OpenAPI at any conventional path on any host, no docs/developers/api host in DNS, no
GraphQL, no MCP server, no A2A agent card, no SDKs, no CLI, no llms.txt, no .well-known/api-catalog. `apis: []` is deliberate
and correct — nothing was scaffolded or generated for this provider.'
webhooks_undocumented: 'SUPERSEDED 2026-08-13 — this finding was wrong. Orum DOES publish a webhook reference at https://support.orum.com/en-US/orum/article/ART-463-webhooks
(HTTP 200, no credentials required): one event `call-disposition-added`, a `{event, payload, test}` envelope, the 13
documented call properties, HMAC-SHA256 base64 signing in `x-webhook-signature` formatted `t={timestamp},s={sig}` over
`{timestamp}.{body}`, a 2xx-before-processing contract with a ~15s timeout, 8 retries over 30 minutes with exponential
backoff and jitter, no historical replay, and three egress IPs. Captured in asyncapi/orum-com-webhooks.yml. The first
pass missed it because the article is absent from all eight help-center directories and from the site sitemap''s own
nav — the ONLY public path to it is the 2025-04-14 launch blog post, and the un-localised URL that post links to (support.orum.com/orum/article/ART-463-webhooks)
returns a Vercel 502. The reference exists; its discoverability is the actual defect.'
github_org_found: CORRECTS the 2026-08-04 probe of github.com/orumcom (404, "no GitHub org found"). The org is github.com/orumhq
— name "Orum", blog https://orum.com/, email support@orum.com, created 2018-09-23, 4 public repos. Three are forks of
third-party VoIP tooling (SIP.js, hepipe.js, purview); the fourth, sundial_api, is a ~100-line fastify mock server on
localhost:4830 that is a hiring-exercise fixture, NOT a product API, and nothing was derived from it.
chrome_extension_found: A first-party Chrome/Edge extension is published on the Chrome Web Store (id mgldaplfkpdgnojhbmllomokgeabokdd,
publisher "Orum", developer email publisher@orum.com, host permissions *://*.orum.com/*), v0.1.1, updated 2026-02-25,
~6,000 users. It is the only versioned first-party distribution Orum ships. It is NOT an SDK, so no SDKs pointer was
emitted.
security_txt_belongs_to_atlassian: status.orum.com/.well-known/security.txt returns HTTP 200, but the document is Atlassian's
— signed by security@atlassian.com with Canonical https://www.atlassian.com/.well-known/security.txt — because status.orum.com
is Atlassian Statuspage infrastructure. Orum serves no security.txt of its own on any host it controls, so no WellKnown
and no SecurityTxt pointer was emitted. Publishing one at www.orum.com pointing at the existing /responsible_disclosure
page and security@orum.com is the cheapest remaining fix.
no_idempotency: Orum retries webhook delivery up to 8 times over 30 minutes on any non-2xx or timeout, but publishes no
idempotency key, no delivery id in the payload, and no de-duplication guidance. Duplicate delivery is expected and the
consumer has nothing to de-duplicate on. No Idempotency pointer was emitted, because there is no idempotency contract.
two_broken_footer_links: /software_and_services_agreement (footer, legal) and /oauth (nav, "Sign in") both 404 to a plain
GET. Worth telling them if the relationship ever warrants it.
competitive_claim_corrected: The graph8 call characterized Orum as "about $250 per seat, a year contract and a minimum
of 10 seats." Orum's published pricing page shows no dollar figure, a 3-seat minimum, and a 500-dial free trial. Thomas's
competitive framing does not match what Orum publishes.
x-enrichment:
date: '2026-08-13'
status: enriched
artifacts_added: 16
pass: local-v1
Orum API — frequently asked questions
How do I authenticate with the Orum API?
Orum uses bearer-token authentication (saml/openIdConnect/oauth2/hmac-signature · 2 schemes). The details are profiled on APIs.io as Orum Com Authentication.
How much does the Orum API cost?
Orum publishes its prices; its Ascend (request pricing) plan is Request pricing as of 2026-10-28. APIs.io lists 1 pricing plan for Orum, with each plan's price, limits and inclusions under Pricing on this page.
Is the Orum API ready for AI agents?
Orum has a Kin Score of 49.4 out of 100 (developing) and an Agent Readiness score of 22.3 (agent-aware), scored by API Evangelist on 2026-11-06.
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.