01 · Records and state owned
Subscribers, phone/email channels, custom attributes, events, transactional or triggered messages, products, and webhook notifications.
Attentive
Attentive
Attentive combines unified customer profiles, real-time signals, and governed messaging across SMS, email, RCS, and push, with APIs plus an announced MCP beta.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve authorized subscriber, event, message, and catalog/integration data exposed by Attentive’s APIs and webhooks.
03 · Actions and write paths
Create or update subscribers and attributes, submit events, and invoke supported messaging or commerce-integration actions under approved use cases.
04 · Authentication and permissions
Private API apps use an app API key as a bearer token; public apps use OAuth 2.0 authorization code flow with requested scopes and user authorization.
05 · Monitoring, approval, and recovery
Consent, opt-in provenance, suppression, quiet hours, transactional-versus-marketing classification, and send authority are non-negotiable.
06 · Limits and caveats
Most API endpoints allow 150 requests per second; identity and subscribe allow 10, unsubscribe 5, and product-catalog uploads 1. Exceeding limits returns 429.
Agent access
MCP support
Product claim unresolvedAttentive-announced MCP beta; technical provider surface unresolvedProduct claim; technical maturity unresolved
Support: Product claim unresolved
Read scope: Attentive has announced a first-party MCP beta, but no public tool catalog or documented MCP read scope was verified.
Write scope: No public Attentive source reviewed here documents MCP mutations, message generation, campaign activation, subscriber changes, or send authority for the beta.
Authentication: Not documented for the announced MCP beta. Attentive's separate API surface uses bearer API keys for private apps and OAuth authorization code flow for public apps.
Approval boundary: Until Attentive documents beta controls, require separate confirmation for subscriber identity, consent changes, message content, audience, channel, marketing-versus-transactional classification, schedule, and send or journey activation.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Attentive ships them.
Single-platform patterns
- Consent-aware mobile messaging and campaign cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Attentive + CRM or commerce system: lifecycle journey debugger
- Attentive + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
APIRepresentative source
https://docs.attentivemobile.com/openapi/reference/overview/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Recorded first-party developer source; summary not endpoint-exhaustive
Developer docsSource inventory
https://docs.attentivemobile.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.attentive.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://docs.attentive.com/me/docs/create-and-manage-webhooks ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.