01 · Records and state owned
Account, person, firmographic, technographic, hierarchy, engagement, intent, buying-group and related B2B intelligence under existing Demandbase permissions
Demandbase
Demandbase One
Curated anchor platform in abm and b2b intelligence with material relevance to the Marcom operating stack and a first-party developer surface.
CRM, revenue & customerSystem of recordAgent-accessible 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
Account, person, firmographic, technographic, hierarchy, engagement, intent, buying-group and related B2B intelligence under existing Demandbase permissions
03 · Actions and write paths
The targeted review confirmed this Demandbase One capability surface: Account, person, firmographic, technographic, hierarchy, engagement, intent, buying-group and related B2B intelligence under existing Demandbase permissions. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.
04 · Authentication and permissions
For Demandbase One, the audited authentication model is: Authentication model is documented by the vendor; inspect the cited source before implementation. The effective permission model is: Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary. Reconfirm the cited first-party source before implementation.
05 · Monitoring, approval, and recovery
Official Demandbase documentation confirms beta availability, per-user authorization and enablement requirements; do not present as universally enabled GA. Official Demandbase documentation confirms beta availability, per-user authorization and enablement requirements; do not present as universally enabled GA.
06 · Gaps and implementation limits
Official Demandbase documentation confirms beta availability, per-user authorization and enablement requirements; do not present as universally enabled GA.
Agent access
MCP and adjacent posture
Verified first-party provider MCPVendor-hosted remote MCPBeta
Role: provider
Read scope: Account, person, firmographic, technographic, hierarchy, engagement, intent, buying-group and related B2B intelligence under existing Demandbase permissions
Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official Demandbase documentation confirms beta availability, per-user authorization and enablement requirements; do not present as universally enabled GA.
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 access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Demandbase ships these experiences.
Single-platform patterns
- ABM account journey and activation cockpit
- Account journey room
- Pipeline-quality debugger
- Customer expansion cockpit
Multi-platform compositions
- Demandbase One + marketing or intent platform: account journey room
- Demandbase One + conversation or support system + analytics or warehouse: 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.
5 recorded sources
MCP / agent-role validationRepresentative source
https://support.demandbase.com/hc/en-us/articles/39507189421979-Set-Up-Demandbase-MCP ↗Official Demandbase documentation confirms beta availability, per-user authorization and enablement requirements; do not present as universally enabled GA.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
MCPSource inventory
https://developer.demandbase.com/docs/mcp ↗First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
APISource inventory
https://developer.demandbase.com/reference/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://developer.demandbase.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.demandbase.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 22, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
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.