Agent report card
Can an agent use Notion API through API integration lifecycle?
Grade C+: Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
Notion / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateLimited
- Sign upLimited
- PayReady
- ProvisionLimited
- OperateLimited
Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
Only some material eligibility conditions are decidable before commitment.
The pricing model is visible but omits a material variable or condition.
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshOnly some material eligibility conditions are decidable before commitment.
Notion defines eligibility parameters for internal connections, public connections, and personal access tokens. Public connections require an explicit installation scope choice (any workspace or selected workspaces) and must undergo a Notion security review to be listed on the Marketplace, but full eligibility criteria for all workspace roles and accounts are not completely specified.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshThe pricing model is visible but omits a material variable or condition.
Notion publishes workspace plan pricing, but the retained evidence does not explicitly isolate the API usage price or no-charge status.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
Notion API documentation provides stable public entrypoints, including a documentation index at /llms.txt, API Reference, and Quickstart guide.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshTerms are readable but materially incomplete, ambiguous, contextual, or unstable.
The documentation identifies that the Master Subscription Agreement governs Notion subscriptions for organizations and Personal Use Terms of Service governs personal use, but the full terms text is not provided in the capture.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
What would improve this stage
- Publish complete applicable terms at a stable public URL.
- State every material eligibility condition and required input explicitly.
- Publish readable complete pricing or explicit no-charge status and conditions.
The access route works but is conditional, tenant-specific, or unstable.
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 evidence for app.notion.com/signup consists of metadata and an incomplete content shell ('Notion'), which does not contain actionable registration form controls, fields, or validation handoffs.
Is there a stable route to begin obtaining service access?
supported: freshThe access route works but is conditional, tenant-specific, or unstable.
The canonical HTTPS signup route resolves to Notion and exposes first-party metadata, but the capture does not establish the complete rendered start flow.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The captured evidence for the signup pages contains only metadata and minimal content shells, which do not show or explicitly declare whether a CAPTCHA challenge is present or absent.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Notion explicitly documents authorization flows including public connections using OAuth 2.0 with access tokens and refresh tokens, as well as token refresh mechanics via POST requests to https://api.notion.com/v1/oauth/token.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained signup page evidence provides metadata showing format-detection telephone=no, but does not explicitly detail phone verification steps or resumable handoff behavior.
What would improve this stage
- Publish one stable canonical access bootstrap entrypoint.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
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 documentation describes upgrading a Notion plan via workspace settings and clicking 'Upgrade now', but it does not establish deterministic API or agent flow controls, approval handoff mechanisms, or programmatic resumption after approval.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Notion's pricing page discloses commercial commitments prior to authorization, specifying plan prices starting at $0 USD per member/month with options to select monthly or yearly payment modes.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
While Notion documents supported payment methods including debit/credit cards, Apple Pay, and Google Pay processed via Stripe, the evidence does not detail a documented rail for scoped delegation or explicit human-confirmed authorization 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 self-service upgrade path where workspace users can navigate to Settings -> Upgrade plan, select a plan, review the order summary, and click 'Upgrade now' to immediately activate paid access without a vendor review or decision point.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
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 that connections exchange an authorization code for an access_token via a POST request to /v1/oauth/token. However, obtaining the initial credentials (CLIENT_ID and CLIENT_SECRET) requires retrieving them manually from 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 via a synchronous POST request returns a page object containing the page id and URL upon success, or a JSON error object with status, code, and message upon failure.
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 sending a POST request to https://api.notion.com/v1/pages with the required JSON payload and 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.
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?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Notion documents token lifecycle support for refreshing access tokens via POST requests to /v1/oauth/token with a refresh_token, returning a new access token and refresh token. Complete lifecycle management including revocation, compromise, and recovery is not fully documented in the provided text.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Notion documents error codes, rate limits, and retry guidance, but not complete idempotency, cancellation, and reconciliation semantics.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Request-time authentication with scoped authority is documented using Bearer tokens (including internal connection tokens and Personal Access Tokens) in the Authorization header along with the Notion-Version header.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Notion documents stable operation contracts across its API endpoints, including input parameters, JSON request bodies, HTTP headers, response schemas, async task handling, rate limits, and error status codes.
- 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 assessed target is accessible via a usable machine-operable interface, including the Notion REST API and the official JavaScript SDK (@notionhq/client).
- 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
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
What blocks agents
- Evaluate: Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
- Sign up: The access route works but is conditional, tenant-specific, or unstable.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
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
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xd8y5ms1v7q3kc9pg2
- Projection
- sha256:26dfec6c51d147a6a12334facc765611fd447c9d09ef1ff1d84f26ebf0cab692
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration