# Pinecone Status Page Monitor

> Pinecone Status Page Monitor is a paid API for AI agents from monitor.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-01).

Fetches the current operational status of Pinecone (vector database service) by reading its public status page at status.pinecone.io

## Facts

- Endpoint: GET https://monitor.intel.rallylive.ca/monitor/status/pinecone?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pinecone-status-page-monitor-a547d085
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PiEBaNPa-yOmj5lmBbqoU

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-status-page-monitor-a547d085
```

Example prompt: Can you check whether Pinecone is currently up and operational, and let me know if there are any active incidents or outages before I keep debugging my vector search integration?

## When to prefer this

Use this endpoint when you need to quickly determine whether Pinecone (the vector database/embedding index service) is experiencing a service disruption before blaming your own code or integration. It is preferable over manually visiting status.pinecone.io or writing custom scraping logic, and is especially useful in automated troubleshooting workflows or pre-flight checks before running Pinecone-dependent tasks.

## Known failure modes

- status.pinecone.io is itself unreachable or returns an error — the monitor may return an unknown or error state
- Pinecone changes their status page format, causing parsing to fail or return incomplete data
- Network timeout when fetching the remote status page
- False negatives: Pinecone reports operational but individual API endpoints may still be degraded

## How this service works

pinecone status right now: reads the vendor's public status page (status.pinecone.io); Statuspage-style pages give the overall indicator (none/minor/major/critical), description and active incidents with impact and last update; other pages are sniffed for operational/outage wording. Ask before blaming your own integration. $0.01 per check.

## Output

Returns the overall Pinecone service status indicator (none/minor/major/critical), a human-readable status description, and details about any active incidents including their impact level and most recent update timestamp.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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-status-page-monitor-a547d085/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from monitor.intel.rallylive.ca](https://www.zero.xyz/host/monitor.intel.rallylive.ca/llms.txt)