Agent report card
Can an agent use Notion API through API integration lifecycle?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upReady
- PayReady
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
The REST API service and its entrypoints are explicitly discoverable via Notion Docs, providing stable integration paths to read, create, and update workspace content.
Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
Price or no-charge status, variables, currency, and material conditions are explicit.
Verified structured artifacts accelerate discovery of the evaluation surface.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence from the Notion Docs overview describes connection types, scopes, and capabilities, but does not explicitly declare pre-commitment material eligibility conditions or restricted inputs such as age, location, or authority.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Notion's pricing page states its prices in US dollars with monthly or yearly payment and a Free plan at $0 per member per month; API integrations are included in the workspace plan, so the price of using the service is decidable before commitment.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
The REST API service and its entrypoints are explicitly discoverable via Notion Docs, providing stable integration paths to read, create, and update workspace content.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
Structured evaluation discovery is available via a verified machine-readable documentation index located at /llms.txt.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshTerms are readable but materially incomplete, ambiguous, contextual, or unstable.
Applicable commitment terms are readable and retrievable via links to the Master Subscription Agreement and Personal Use Terms of Service, but the agreement bodies themselves are not included in the captured evidence.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence references fetching /llms.txt for documentation indexing, but does not explicitly declare a web agent access policy or web crawler rules such as robots.txt directives.
A stable canonical route begins the required access bootstrap.
A stable canonical access URL for signup (https://app.notion.com/signup) is established by direct observation.
Scoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained page capture for signup contains only application shell metadata and lacks readable form controls, validation elements, or handoff controls to assess access control operability.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable canonical access URL for signup (https://app.notion.com/signup) is established by direct observation.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained captures for the signup endpoint and resource contain only application shell metadata, leaving the presence or absence of a mandatory CAPTCHA unresolved.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Notion documentation explicitly specifies authorization flows for personal access tokens, internal connections, and public connections using OAuth 2.0 with access and refresh tokens.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained signup capture contains metadata and does not explicitly declare whether phone verification is required, absent, or resumable.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
The pricing schedule discloses plan tiers, including the Free tier at $0 and the Plus tier at $10 per member/month in USD, along with monthly and annual billing modes.
A documented direct purchase path reaches paid access without a vendor decision point.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence describes upgrading a plan by clicking Settings -> Upgrade plan and selecting Upgrade now, but it does not establish deterministic checkout construction, handoff approval, and safe resumption required for a yes finding.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
The pricing schedule discloses plan tiers, including the Free tier at $0 and the Plus tier at $10 per member/month in USD, along with monthly and annual billing modes.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The evidence outlines workspace owners approving member upgrade requests, but it does not document a full scoped delegation rail or explicit human authorization mechanism with receipts.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
Notion documents a direct direct self-service path to upgrade plans under Settings -> Upgrade plan, where users can review an order summary and click Upgrade now without vendor intervention.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Notion documents exchanging an authorization code for an access token via an HTTP POST request to Notion's token endpoint. Retrieval of CLIENT_ID and CLIENT_SECRET requires accessing the Developer portal.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
Notion documents exchanging an authorization code for an access token via an HTTP POST request to Notion's token endpoint. Retrieval of CLIENT_ID and CLIENT_SECRET requires accessing the Developer portal.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshA synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Creating a page returns a synchronous page object containing the page id, created time, and URL upon success.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Page creation can be initiated programmatically by making a POST request to https://api.notion.com/v1/pages with an authorization token.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
Safe failure handling is documented only partially.
Notion documents status codes including 429, 409 conflicts and 529 overload with Retry-After guidance; the selected quotes do not establish idempotency or reconciliation semantics for page creation.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Essential operations have stable readable request, response, and effect semantics.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts describe REST or RPC interfaces, SDKs and CLIs for Notion API; they contain no first-party statement that an agent-native protocol interface is absent, and several navigation excerpts mention MCP resources without establishing coverage of the assessed targets.
- content-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
The documentation explicitly describes refreshing an access token via POST /v1/oauth/token to receive a new access token and refresh token, but leaves administrative key revocation and compromise recovery procedures for all credential types partially documented.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Notion documents status codes including 429, 409 conflicts and 529 overload with Retry-After guidance; the selected quotes do not establish idempotency or reconciliation semantics for page creation.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Notion API requests are authenticated using Bearer tokens in the Authorization header for personal access tokens and internal connections, and OAuth 2.0 bearer tokens for public connections.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Essential operations across all evaluated surfaces have documented readable request schemas, response codes, parameters, and rate limit contracts.
- content-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Every essential target surface provides a machine-operable HTTP REST API interface for agent interaction.
- content-api
What would improve this stage
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
- Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
- Sign up: A stable canonical route begins the required access bootstrap.
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
What blocks agents
No stage is established as blocked.
Where autonomy is limited
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
What this grade establishes
14 of 14 graded signals have current supporting evidence. 0 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.
How the grade is derived
A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.
Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.
Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.
Startup offers
Notion on the startup-offers board
- Up to 6 months free of the Notion Business plan with Notion AI includedUp to 6 months of Notion Business free with Notion AI
Distribution
The grade’s badge
One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.
[](https://sourcey.com/log/notion/agent-readiness/notion-api/api-integration-lifecycle)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xd8y5ms1v7q3kc9pg2
- Projection
- sha256:3b0115c08e61c01442c468a8abd1459402678e6514f70b221229e072acc738fb
- Policy
- service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration