Agent report card
Can an agent use Neon API through Project and database lifecycle?
Grade C+: Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
Neon / 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 exact service and stable evaluation or access entrypoints are publicly discoverable.
Price or no-charge status, variables, currency, and material conditions are explicit.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshOnly some material eligibility conditions are decidable before commitment.
The Product Specific Schedule governs Customer's use of Databricks' Neon product family. Accessing Platform Services binds the customer to the Schedule, and individuals entering into it on behalf of a company represent and warrant that they are authorized to bind that legal entity.
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.
Neon pricing establishes a Free plan at $0 with specific limits (100 projects, 100 CU-hrs monthly per project, 0.5 GB storage per project) with no credit card required, as well as paid usage pricing details such as extra branches billed at $1.50 per extra branch-month ($0.002 per hour).
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 Neon API reference provides the exact service endpoints and base URL (https://console.neon.tech/api/v2/), along with links to the Neon OpenAPI Specification in JSON format.
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 Product Specific Schedule for Neon Cloud Computing Platform Services is retrievable, but explicitly incorporates the then-current Databricks Master Cloud Services Agreement located at https://www.databricks.com/legal/mcsa and usage-based plan documentation located at https://neon.com/docs/introduction/plans.
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.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
A stable canonical route begins the required access bootstrap.
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 signup endpoint for console.neon.tech returned an HTTP 403 Cloudflare security verification challenge page, leaving the operability of the access controls unresolved in the admissible evidence.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Neon documentation provides stable canonical navigation entrypoints to Log in and Sign up to begin obtaining service access.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
A captured Cloudflare security response does not establish a mandatory CAPTCHA across the actual registration flow.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Neon supports Personal, Organization, and Project-scoped API keys with specific access scopes and immediate revocation capabilities, but creating the initial API key requires manual action in the Neon Console where the secret token is displayed only once.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained documentation details password changes, two-factor authentication via authenticator apps, and passkeys, but does not state phone verification requirements.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
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.
Admitted evidence describes plan pricing and billing management options in the Neon Console, but does not document an API, protocol, or web flow for an agent to construct checkout, hand off approval safely, and resume.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Neon discloses its pricing structure on the pricing page. The Free plan is $0, while the Launch plan ($0.106 per CU-hour) and Scale plan ($0.222 per CU-hour) are usage-based ('Pay for what you use') with USD currency and specific hourly compute rates.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
Retained evidence outlines billing methods, auto-debit on the first day of the month, and manual invoice payment by account owners/admins, but does not define a documented authorization rail for scoped agent 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.
Neon documentation provides a direct self-service path to paid access. Users can start for free and change plans (Launch or Scale) or update payment methods directly from the Billing page in the Neon Console without a required vendor decision point.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
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.
When creating API keys from the Neon Console, the secret token is displayed only once and cannot be retrieved later. Users must manually copy it immediately and store it securely.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshCompletion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
When creating a project via API, a 201 response returns a project object with connection details, but users must wait for background operations to finish before connecting. Branch creation exposes asynchronous operation progress statuses like 'running' and 'scheduling'.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Provisioning can be initiated programmatically within supported agent authority via the Neon API, such as calling POST /projects to create a project or POST /projects/{project_id}/branches to create a branch.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
- Expose bounded machine-readable terminal status and reconciliation semantics.
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.
Neon documents creating and revoking API keys, as well as manually rotating them by creating a replacement and revoking the old key. Revocation is immediate and permanent, and compromised keys should be revoked immediately. However, API keys do not expire or rotate on a schedule.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Neon API exposes asynchronous operations with an explicit failure count and operational state tracking (such as running or scheduling) for branch and project actions. However, full safe retry, cancellation, idempotency, and reconciliation semantics across all failure modes are not completely detailed in the provided documentation.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Neon supports request-time API key authentication via the standard HTTP Authorization header using the Bearer scheme (`Authorization: Bearer $NEON_API_KEY`). API keys can be scoped to personal, organization, or single project access.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
The Neon API provides stable, readable endpoints, schemas, request parameters, response objects, and HTTP status code behaviors for essential operations such as managing projects, branches, and API keys.
- project-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—including project management, branch operations, and API key management—has documented, agent-usable HTTP REST API endpoints.
- project-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: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
Startup offers
Neon on the startup-offers board
- Up to $1,000 in Neon creditsNeon Startup Program - Self-Funded
- Up to $200K in creditsNeon Startup Program - Venture-Backed
- Up to $200,000 in Neon and Databricks credits valid for 12 months.Databricks Startup Program - Venture-Backed
- Up to $1,000 in Neon credits valid for 12 months.Databricks Startup Program - Self-Funded
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xc6w3hq8r2f9bj5nta
- Projection
- sha256:2a146c4a98d05800c8b85e274347b82a27008b3ce4ccd34440c54196be49e6ec
- 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