Agent report card
Can an agent use Pinecone Database API through Index lifecycle?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayReady
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Pinecone provides public API documentation detailing the exact Database API. It covers core resources like indexes and vectors, along with supported client SDKs including Python, Node.js, Java, and Go.
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.
Verified structured artifacts accelerate discovery of the evaluation surface.
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 specifies that individual users must be legally permitted and competent to enter into the agreement, and users on behalf of an entity represent that they have full legal right, power, and authority to bind the customer.
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's pricing page outlines explicit plan rates and conditions, including a free Starter tier, $20/month flat for Builder, $50/month minimum for Standard (with pay-as-you-go after exceeding), and $500/month minimum for Enterprise.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
Pinecone provides public API documentation detailing the exact Database API. It covers core resources like indexes and vectors, along with supported client SDKs including Python, Node.js, Java, and Go.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
Pinecone explicitly offers a verified machine-readable discovery artifact, directing clients to fetch the complete documentation index at /llms.txt.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
Pinecone's Master Subscription Agreement provides readable and retrieveable legal terms governing the purchase and use of Pinecone's Services.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
While the documentation index references /llms.txt, the retained evidence does not contain explicit declarations or verified access policies governing web agents, crawlers, or robots.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Pinecone documentation states that service accounts enable programmatic access to the Admin API and use client secrets to retrieve access tokens. However, creating a service account and retrieving its initial client secret requires manual actions in the Pinecone console.
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 captured Pinecone Console landing page contains only an application shell titled 'Pinecone Console'. Current evidence does not provide readable interactive form fields, controls, or validation steps to establish access control operability.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Pinecone documentation provides visible canonical entry points to 'Log in' and 'Sign up free' to begin obtaining service access.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence across the console and documentation surfaces does not contain an explicit declaration or observation regarding CAPTCHA boundaries or verified-agent alternatives.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Pinecone documentation states that service accounts enable programmatic access to the Admin API and use client secrets to retrieve access tokens. However, creating a service account and retrieving its initial client secret requires manual actions in the Pinecone console.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained console and documentation pages make no mention of phone verification requirements, delegation, or resumable verification handoffs.
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.
Pinecone's pricing page discloses the commercial commitments for its plans, such as $20/month flat for the Builder plan and $50/month minimum usage (pay-as-you-go above that) for the Standard plan.
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 switching payment methods between credit cards and marketplaces, but does not provide evidence for an API or accessible web flow supporting deterministic checkout, bounded authorization handoff, and resumption.
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 discloses the commercial commitments for its plans, such as $20/month flat for the Builder plan and $50/month minimum usage (pay-as-you-go above that) for the Standard plan.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The documentation notes that changing payment methods requires being an organization owner or billing admin, but does not describe a payment authorization rail with scoped delegation or 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 upgrade path in the console under Settings > Billing > Plans, where users can select Upgrade on the Standard or Enterprise plan section and enter credit card information to complete paid access.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
API keys are generated in the Pinecone console. Service accounts created in the console provide client secrets that are displayed once at creation and used to retrieve access tokens.
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.
API keys are generated in the Pinecone console. Service accounts created in the console provide client secrets that are displayed once at creation and used to retrieve access tokens.
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.
The Create Index API response returns an IndexModel containing host and status fields (such as ready: true and state: Ready), exposing progress and ready states, but the retained evidence leaves reconciliation after asynchronous failure unresolved.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Index provisioning is machine-triggerable via POST requests to /indexes using an API key header.
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.
Pinecone documents HTTP error semantics and exponential-backoff retry guidance for 429 and 5xx; the selected quotes do not establish idempotency, cancellation or reconciliation semantics for index operations.
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.
Pinecone documentation describes REST APIs and SDKs for Database and Inference. The retained excerpts do not establish a verified agent-native protocol interface such as MCP or A2A.
- index-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
The retained evidence documents rotated client secrets for service accounts and service account deletion in the Pinecone console, as well as API key authentication for project operations. However, full programmatic agent-driven key rotation, revocation, and recovery without console involvement are not fully established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Pinecone documents HTTP error semantics and exponential-backoff retry guidance for 429 and 5xx; the selected quotes do not establish idempotency, cancellation or reconciliation semantics for index operations.
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 require an Api-Key HTTP header for the target project or OAuth access tokens (Bearer tokens) retrieved via client credentials for Admin API operations.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Pinecone provides decidable request schemas, method endpoints, and structured responses across control plane operations like creating indexes and defines status codes and system limits.
- 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.
Pinecone provides machine-operable interfaces including curl REST endpoints, a CLI, and SDKs in Python, JavaScript, Java, and Go across database 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.
- 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
- 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.
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
Pinecone on the startup-offers board
- Free Standard Tier access, Pro Support, usage credits, and discountsPinecone for Startups
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/pinecone/agent-readiness/pinecone-database-api/index-lifecycle)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xf5d9pv2y8s1jm6rw3
- Projection
- sha256:401c511096dea81f1a41b4602f4ea4b66f7d7ef28267e04e60eb14680eddc498
- 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