# Pinecone Vector Upsert via Sovereign x402

> Pinecone Vector Upsert via Sovereign x402 is a paid API for AI agents from sovereign-x402-zeta.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Upserts (inserts or updates) vectors into an existing Pinecone index, paid per call via x402 micropayment.

## Facts

- Endpoint: POST https://sovereign-x402-zeta.vercel.app/api/v1/vector/pinecone/upsert
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pinecone-vector-upsert-via-sovereign-x402-8a93d15d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A1xR1-FO85WGxw49nBVOh

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability pinecone-vector-upsert-via-sovereign-x402-8a93d15d -d '<json body>'
```

Example prompt: Store these two 2-dimensional vectors into my Pinecone 'test-index' — vector ID 'vec1' with values [0.1, 0.9] and vector ID 'vec2' with values [0.5, 0.5].

## When to prefer this

Choose this endpoint when you need a pay-per-call, no-setup-required way to upsert vectors into Pinecone via an x402-enabled micropayment flow, especially useful for agents that need programmatic vector storage without managing Pinecone credentials directly. Prefer it in agentic pipelines where per-call billing is preferable to subscription management.

## Known failure modes

- Index does not exist in the Pinecone project — the target index must be pre-created
- Vector dimension mismatch — submitted vectors must match the index's configured dimension (2 for 'test-index')
- Malformed request body — missing required fields like vector IDs or values
- Payment failure — x402 micropayment of $0.005 USDC not processed correctly
- Pinecone API key or project misconfiguration on the server side

## How this service works

Upsert vectors into a Pinecone index (index must already exist in your Pinecone project -- 'test-index', dimension 2, is kept live for exactly this example).

## Output

Returns a confirmation from Pinecone indicating how many vectors were successfully upserted into the specified index, typically including an upserted count field.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {},
     "additionalProperties": true
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pinecone-vector-upsert-via-sovereign-x402-8a93d15d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sovereign-x402-zeta.vercel.app](https://www.zero.xyz/host/sovereign-x402-zeta.vercel.app/llms.txt)