Agent report card
Can an agent use Notion API through API integration lifecycle?
Grade D: Only part of the applicable terms is machine-readable.
notion / active
Five-stage assessment
Where agent autonomy holds and where it breaks
First break: Evaluate
Evaluate
LimitedOnly part of the applicable terms is machine-readable.
Decidable eligibility has not been established.
An ARD declaration has not been established.
An agent can discover the product and funnel from the tested public entrypoints.
Pricing or the absence of a charge is explicit and machine-readable.
Evidence and actions
ARD declaration unknown
missing: unknownAn ARD declaration has not been established.
Decidable eligibility unknown
supported: freshDecidable eligibility has not been established.
The retained terms text provides metadata and title info, but lacks explicit criteria to establish decidable eligibility.
Machine discovery
supported: freshAn agent can discover the product and funnel from the tested public entrypoints.
Machine discovery is supported via canonical links and explicit document references to llms.txt and API navigation routes.
Readable pricing
supported: freshPricing or the absence of a charge is explicit and machine-readable.
Pricing details across Free, Plus, and Business tiers with specific pricing values are explicitly published and machine-readable.
Structured terms limited
supported: freshOnly part of the applicable terms is machine-readable.
Terms are published via HTML, representing a readable but un-structured terms contract format.
What would improve this stage
- Publish complete applicable terms in a stable machine-readable document.
Sign up
ReadyA stable signup entrypoint is available.
The tested signup flow exposes machine-operable controls.
No CAPTCHA was encountered on the tested signup path.
The tested signup path does not require phone or SMS verification.
A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.
Evidence and actions
CAPTCHA-free signup
supported: freshNo CAPTCHA was encountered on the tested signup path.
No CAPTCHA challenge was encountered on the Notion signup page during headless evaluation.
Machine-operable signup
supported: freshThe tested signup flow exposes machine-operable controls.
The account creation page presents standard machine-operable form controls, including input fields for work email and submission buttons.
Phone-free signup
supported: freshThe tested signup path does not require phone or SMS verification.
The signup interface allows registration using work email or single sign-on without requiring phone or SMS verification.
Stable signup entrypoint
supported: freshA stable signup entrypoint is available.
The signup URL returned a valid and stable HTTP response.
Supported identity flow
supported: freshA scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.
Notion documents scoped and revocable authorization flows, including OAuth 2.0 public connections with explicit user page-picking consent and internal integration tokens.
Pay
BlockedThe required checkout cannot be operated by an agent.
No supported payment rail is available for the tested funnel.
The required price or no-charge status is explicit before commitment.
The tested funnel can complete without sales intervention.
Evidence and actions
Explicit price
supported: freshThe required price or no-charge status is explicit before commitment.
Notion explicitly publishes plan pricing details (e.g. Free at $0, Plus at $10/member/month, Business at $20/member/month) on its public pricing page.
Machine-operable checkout unavailable
supported: freshThe required checkout cannot be operated by an agent.
The signup flow at app.notion.com presents interactive email and single sign-on registration forms that require human interaction rather than a machine-operable API checkout.
Sales-free purchase
supported: freshThe tested funnel can complete without sales intervention.
The standard account creation and onboarding flow allows self-service signup via work email or direct provider authentication (Google/Microsoft) without sales intervention.
Supported payment rail unavailable
supported: freshNo supported payment rail is available for the tested funnel.
The workspace signup flow does not expose an automated or supported programmatic payment rail for machine operations.
What blocks agents
- The required checkout cannot be operated by an agent.
- No supported payment rail is available for the tested funnel.
What would improve this stage
- Expose documented, labelled checkout controls or an agent-compatible commerce interface.
- Document a supported payment rail, authorization boundary, receipts, and failure semantics.
Provision
LimitedOnly part of the provisioning lifecycle exposes machine-readable status.
A bounded provisioning delay has not been established.
Successful onboarding automatically activates usable access.
Usable credentials or delegated access are delivered through a documented flow.
Evidence and actions
Automatic activation
supported: freshSuccessful onboarding automatically activates usable access.
Notion API quickstart shows that creating a personal access token automatically grants usable access for immediate page creation requests.
Bounded provisioning delay unknown
supported: freshA bounded provisioning delay has not been established.
Notion documentation specifies rate limits and retry guidelines, but does not provide an explicit bounded timing guarantee for API request or credential provisioning.
Credential delivery
supported: freshUsable credentials or delegated access are delivered through a documented flow.
Notion delivers usable credentials via static tokens for internal connections and PATs, and via an OAuth 2.0 exchange endpoint delivering an access_token and refresh_token for public connections.
Machine-readable provisioning status limited
supported: freshOnly part of the provisioning lifecycle exposes machine-readable status.
Notion documents structured machine-readable status and error codes (such as rate_limited and HTTP 429/529 errors), but does not detail complete machine-readable asynchronous progress, reconciliation, or cancellation status for all provisioning stages.
What would improve this stage
- Expose deterministic provisioning progress, terminal states, errors, cancellation, and reconciliation where applicable.
Operate
LimitedRecovery is available only for some failure modes or requires human intervention.
An agent protocol interface has not been established.
A documented API or tool interface is available for operation.
Authentication is documented and usable within an agent authorization boundary.
Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.
Evidence and actions
Agent protocol interface unknown
missing: unknownAn agent protocol interface has not been established.
API or tool access
supported: freshA documented API or tool interface is available for operation.
Notion provides a documented REST API allowing machine access to pages, databases, users, comments, and other workspace content.
Delegated recovery limited
supported: freshRecovery is available only for some failure modes or requires human intervention.
Status code documentation provides retry guidance for transient errors, conflicts, and rate limits, but full credential rotation and recovery pathways require human intervention or standard OAuth handling.
Documented limits and errors
supported: freshLimits, structured errors, retry behavior, and idempotency semantics are documented where applicable.
Notion documents rate limits, parameter size limits, structured error codes, Retry-After header guidance, and explicit idempotency semantics for retries.
Usable authentication
supported: freshAuthentication is documented and usable within an agent authorization boundary.
Notion supports usable agent and application authentication via Bearer tokens for internal connections/PATs and OAuth 2.0 access tokens for public connections.
What would improve this stage
- Provide delegated credential rotation, revocation, retry, and recovery paths without requiring unrestricted human intervention.
What works
- Sign up: A stable signup entrypoint is available.
What blocks agents
- Evaluate: Only part of the applicable terms is machine-readable.
- Pay: The required checkout cannot be operated by an agent.
- Provision: Only part of the provisioning lifecycle exposes machine-readable status.
- Operate: Recovery is available only for some failure modes or requires human intervention.
Improve the report
Correct it, rerun it, or improve the funnel
Every request carries the exact profile revision, projection, declaration, and Catalog release.
Method, policy, and immutable identifiers
Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.
Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.
- Profile ID
- arp_01kzf0m4xd8y5ms1v7q3kc9pg2
- Revision
- sha256:9a87be92ab1e3705cf482e99015d9a8fd0403a75f650f298e3ababeee826504e
- Projection
- sha256:eae5245d11e8ef3c221d0706d7fde6c674ce91b807a2aa7f648588796f667c64
- Policy
- service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
- Base Catalog release
- sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6