Embrace is a user-focused observability platform for mobile and web applications, built on OpenTelemetry. Its SDKs for iOS, Android, React Native, Flutter, Unity and the browser capture full-fidelity session, crash, exception, log, trace and network telemetry from real users, and the platform turns that into crash-free rates, user journeys, synthetics and custom dashboards. For programmatic access Embrace publishes a Prometheus-compatible Metrics API queried with PromQL, a Custom Metrics API for creating and managing derived metrics, OTLP forwarding to third-party destinations such as Datadog, Grafana Cloud, New Relic, Honeycomb, Elastic, Splunk, Chronosphere and Observe, outgoing alert webhooks, and a hosted Model Context Protocol server that exposes 21 read tools over crash, exception, log, span, session and network data to AI assistants using OAuth 2.0 or service-account bearer tokens.
Embrace is listed with 3 APIs on the APIs.io network. Tagged areas include Company, Observability, Monitoring, Mobile, and Real User Monitoring.
The Embrace catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Embrace’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 28 more developer resources.
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/embrace/"><img src="https://apis.io/badge/embrace/card.svg" alt="Embrace 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
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
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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.
A Prometheus-compatible read API for querying Embrace metrics with PromQL. Standard Embrace metrics and any Custom Metrics an organization has created are queryable across one a...
A REST management API for creating, retrieving and deleting the custom metrics of an Embrace organization. A custom metric is defined from a base Embrace metric plus group_by di...
A hosted Model Context Protocol server over Streamable HTTP that exposes an Embrace organization's real-user observability data to MCP-capable AI assistants. Twenty-one publishe...
The Embrace MCP server exposes an organization's real-user mobile and web observability data — apps, crashes, exceptions, logs, sessions, spans and network endpoints — to MCP-ca...
aid: embrace
name: Embrace
description: Embrace is a user-focused observability platform for mobile and web applications, built on OpenTelemetry. Its
SDKs for iOS, Android, React Native, Flutter, Unity and the browser capture full-fidelity session, crash, exception, log,
trace and network telemetry from real users, and the platform turns that into crash-free rates, user journeys, synthetics
and custom dashboards. For programmatic access Embrace publishes a Prometheus-compatible Metrics API queried with PromQL,
a Custom Metrics API for creating and managing derived metrics, OTLP forwarding to third-party destinations such as Datadog,
Grafana Cloud, New Relic, Honeycomb, Elastic, Splunk, Chronosphere and Observe, outgoing alert webhooks, and a hosted Model
Context Protocol server that exposes 21 read tools over crash, exception, log, span, session and network data to AI assistants
using OAuth 2.0 or service-account bearer tokens.
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: freemium
onboarding: self-serve
trial: false
try_now: true
public: false
gated: none
gated_source:
- onboarding
label: Freemium · Self-serve signup
confidence: high
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://embrace.io/wp-content/uploads/2023/07/Embrace-Logo-Pref-Lead-on-Yellow_1200x627.png
url: https://raw.githubusercontent.com/api-evangelist/embrace/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Observability
- Monitoring
- Mobile
- Real User Monitoring
- OpenTelemetry
- Metrics
- Crash Reporting
- Application Performance Monitoring
- Developer Tools
- MCP
tags_raw:
- Company
- Observability
- Monitoring
- Mobile
- Real User Monitoring
- OpenTelemetry
- Metrics
- Crash Reporting
- Application Performance Monitoring
- Developer Tools
- Model Context Protocol
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
apis:
- aid: embrace:embrace-metrics-api
name: Embrace Metrics API
description: A Prometheus-compatible read API for querying Embrace metrics with PromQL. Standard Embrace metrics and any
Custom Metrics an organization has created are queryable across one app, several apps, or every app in the organization
by filtering on app_id. Authenticated with the organization's Metrics API bearer token from Settings → Organization →
API. Any PromQL client works against it — the docs ship Node (prometheus-query) and Python (prometheus-api-client) samples
against the /api/v1 Prometheus HTTP API surface.
humanURL: https://embrace.io/docs/metrics-forwarding/metrics-api/
baseURL: https://api.embrace.io/metrics
tags:
- Metrics
- PromQL
- Prometheus
- Observability
- Monitoring
properties:
- type: Documentation
url: https://embrace.io/docs/metrics-forwarding/metrics-api/
- type: APIReference
url: https://embrace.io/docs/metrics-forwarding/metrics-api/
- type: Examples
url: https://embrace.io/docs/metrics-forwarding/metrics-api/code-samples/
- type: Authentication
url: authentication/embrace-authentication.yml
- aid: embrace:embrace-custom-metrics-api
name: Embrace Custom Metrics API
description: A REST management API for creating, retrieving and deleting the custom metrics of an Embrace organization.
A custom metric is defined from a base Embrace metric plus group_by dimensions, a filter tree, one or more time granularities
(five_minute, hourly, daily) and a list of data destinations (metrics_api, newrelic, datadog, grafana_cloud). Authenticated
with a dedicated Custom Metrics API bearer token issued by an Embrace onboarding specialist.
humanURL: https://embrace.io/docs/metrics-forwarding/custom-metrics/custom-metrics-api/
baseURL: https://api.embrace.io/custom-metrics
tags:
- Metrics
- Custom Metrics
- Observability
- Management
- Data Forwarding
properties:
- type: Documentation
url: https://embrace.io/docs/metrics-forwarding/custom-metrics/custom-metrics-api/
- type: APIReference
url: https://embrace.io/docs/metrics-forwarding/custom-metrics/custom-metrics-api/
- type: ErrorCatalog
url: errors/embrace-problem-types.yml
- type: Authentication
url: authentication/embrace-authentication.yml
- aid: embrace:embrace-mcp-server
name: Embrace MCP Server
description: A hosted Model Context Protocol server over Streamable HTTP that exposes an Embrace organization's real-user
observability data to MCP-capable AI assistants. Twenty-one published tools span apps, crashes, exceptions, logs, sessions,
root spans and network domains and endpoints. Authentication is either an interactive OAuth 2.0 authorization-code flow
with PKCE against dash-api.embrace.io, or a static service-account bearer token (emb_sa_ prefix) carrying the mcp:tools:call
scope plus mcp:read and/or mcp:write.
humanURL: https://embrace.io/docs/mcp/
baseURL: https://mcp.embrace.io/mcp
tags:
- MCP
- Agents
- Observability
- Artificial Intelligence
tags_raw:
- Model Context Protocol
- MCP
- Agents
- Observability
- AI
properties:
- type: MCPServer
url: mcp/embrace-mcp.yml
- type: Documentation
url: https://embrace.io/docs/mcp/
- type: OAuthScopes
url: scopes/embrace-scopes.yml
common:
- type: DomainSecurity
url: security/embrace-domain-security.yml
- type: VulnerabilityDisclosure
url: security/embrace-vulnerability-disclosure.yml
- type: Website
url: https://embrace.io/
- type: DeveloperPortal
url: https://embrace.io/docs/
- type: Documentation
url: https://embrace.io/docs/
- type: APIReference
url: https://embrace.io/docs/metrics-forwarding/metrics-api/
- type: GettingStarted
url: https://embrace.io/docs/ios/6x/getting-started/
- type: Support
url: https://embraceio-community.slack.com/join/shared_invite/zt-46iaieyz5-_684dnJ8U1yspqeQf~AGJA
- type: Blog
url: https://embrace.io/blog/
- type: BlogRSS
url: https://embrace.io/feed/
- type: GitHubOrganization
url: https://github.com/embrace-io
- type: Pricing
url: https://embrace.io/pricing/
- type: SignUp
url: https://dash.embrace.io/signup
- type: Login
url: https://dash.embrace.io/login
- type: TermsOfService
url: https://embrace.io/terms-of-service/
- type: PrivacyPolicy
url: https://embrace.io/privacy/
- type: StatusPage
url: https://status.embrace.io/
- type: ChangeLog
url: https://embrace.io/docs/product/changelog/
- type: TrustCenter
url: https://trust.embrace.io/
- type: Packages
url: packages/embrace-packages.yml
- type: SDKs
url: packages/embrace-packages.yml
- type: CLI
url: cli/embrace-cli.yml
- type: WellKnown
url: well-known/embrace-well-known.yml
- type: MCPServer
url: mcp/embrace-mcp.yml
- type: LLMsTxt
url: llms/embrace-llms.txt
- type: Authentication
url: authentication/embrace-authentication.yml
- type: OAuthScopes
url: scopes/embrace-scopes.yml
- type: Conventions
url: conventions/embrace-conventions.yml
- type: ErrorCatalog
url: errors/embrace-problem-types.yml
- type: Lifecycle
url: lifecycle/embrace-lifecycle.yml
- type: Conformance
url: conformance/embrace-conformance.yml
- type: Webhooks
url: asyncapi/embrace-alerts-webhooks.yml
- type: AgentSkill
url: skills/_index.yml
- type: Plans
url: plans/embrace-plans-pricing.yml
- type: RateLimits
url: rate-limits/embrace-rate-limits.yml
x-enrichment:
date: '2026-08-12'
status: enriched
artifacts_added: 28
pass: local-v1
Embrace API — frequently asked questions
Does Embrace have an API?
Yes. APIs.io lists 3 APIs from Embrace, including Embrace Metrics API, Embrace Custom Metrics API and Embrace MCP Server.
How do I authenticate with the Embrace API?
Embrace documents its authentication (http/oauth2 · 5 schemes). The details are profiled on APIs.io as Embrace Authentication.
How much does the Embrace API cost?
Embrace publishes its prices; its FREE plan is $0 as of 2026-10-28. APIs.io lists 3 pricing plans for Embrace, with each plan's price, limits and inclusions under Pricing on this page.
Does Embrace have an MCP server?
Yes. APIs.io lists 1 MCP server for Embrace: The Embrace MCP server exposes an organization's real-user mobile and web observability data — apps, crashes, exceptions, logs, sessions, spans and network endpoints — to MCP-capable AI assistants. Sh
Is the Embrace API ready for AI agents?
Embrace has a Kin Score of 69.3 out of 100 (exemplar) and an Agent Readiness score of 52.2 (agent-ready), 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.