Agent report card
Can an agent use Pinecone Database API through Index lifecycle?
Grade B+: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Pinecone / active
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.
Applicable terms are stable, readable, retrievable, and materially complete.
Eligibility conditions and required inputs are explicit and decidable.
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: freshEligibility conditions and required inputs are explicit and decidable.
Pinecone's Master Subscription Agreement explicitly defines eligibility requirements, stating that individuals using the Services for their own purposes must be legally permitted and competent to enter into the contract, and individuals acting on behalf of an entity represent that they have full legal right, power, and authority to bind that 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.
Pinecone explicitly discloses its pricing model on its pricing page, detailing a free Starter tier as well as paid tiers including Builder at $20/month flat and Standard at $50/month minimum usage, alongside pay-as-you-go options.
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 Pinecone API reference documentation explicitly outlines stable entrypoints and discovery routes for Pinecone Database, Inference, and Admin APIs along with supported SDKs.
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: freshApplicable terms are stable, readable, retrievable, and materially complete.
The Master Subscription Agreement is publicly retrievable and readable, containing the explicit terms and conditions governing the purchase and use of Pinecone's Services.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
A stable canonical route begins the required access bootstrap.
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 capture from https://app.pinecone.io/ returns an application shell ('Pinecone Console') without accessible web form fields or controls, leaving access control operability unresolved.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Pinecone documentation includes functional links to 'Log In' and 'Sign up free', providing a stable entrypoint to begin service access.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained captures across the pinecone application shell and documentation pages contain no explicit declaration or direct observation regarding CAPTCHA requirements or alternative agent access routes.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Pinecone documents API keys scoped to projects and service accounts that enable programmatic access using client secrets and OAuth client credentials via https://login.pinecone.io/oauth/token.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence across the console application shell and documentation pages contains no explicit declaration or direct observation regarding phone verification requirements.
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.
Current admissible evidence does not establish the full deterministic checkout construction, approval handoff, and resumption flow.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Pinecone's pricing page explicitly discloses charge terms, currencies, monthly recurring rates, and min usage commitments, such as the Builder plan at $20/month flat and Standard plan at $50/month minimum usage.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
Documentation states payment methods can be updated by an organization owner or billing admin, but does not detail a delegated agent rail 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.
Pinecone documents a direct self-service path to upgrade to paid Standard or Enterprise plans by navigating to Settings > Billing > Plans, clicking Upgrade, selecting Credit / Debit card, and entering payment details.
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.
Pinecone documentation states that API keys can be created in the Pinecone console or generated via a connect widget, and client secrets for service accounts are displayed once upon creation in the console for manual copying, leaving credential delivery as a manual transfer step.
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.
Creating a Pinecone index returns a synchronous JSON response containing status fields such as ready (boolean), state ('Ready' or 'ScalingUpPodSize'), and host URL, establishing observable completion state but omitting explicit terminal error bounds or reconciliation guarantees.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Pinecone index provisioning can be initiated programmatically within supported agent authority by issuing an HTTP POST request to the https://api.pinecone.io/indexes endpoint using a valid Api-Key header or via SDK methods like CreateServerlessIndex.
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.
Pinecone documents service account client secret rotation and retrieval of an access token via the /oauth/token endpoint. However, rotating a service account secret is documented as a manual action performed in the Pinecone console.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Pinecone documentation details HTTP response status codes for client errors (4xx) and server errors (5xx), and explicitly instructs implementing retry logic with exponential backoff for rate limiting (429) and transient server errors (500, 502, 503, 504). Safe failure handling is only partially documented as cancellation and explicit reconciliation semantics are not established in the evidence.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
All requests to Pinecone APIs must contain an Api-Key header specifying a valid API key for the target project, which can be passed directly in HTTP headers or configured within initialized SDK clients.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
The API reference and database limits endpoints define request schemas, parameters, response object structures, HTTP methods, status codes, and operating limits across all evaluated surfaces.
- index-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.
Machine-operable interfaces including official SDKs (Python, Node.js, Java, Go), a CLI tool, and direct REST HTTP endpoints are provided and documented for all essential operation targets.
- index-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
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
Startup offers
Pinecone on the startup-offers board
- Free Standard Tier access, Pro Support, usage credits, and discountsPinecone for Startups
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xf5d9pv2y8s1jm6rw3
- Projection
- sha256:4719d9b9387d551cba5189db43a928ba2c662b1229dfb1e8c879fc8c865f1093
- 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