# Webber Sites Agent Datastore — List Collections

> Webber Sites Agent Datastore — List Collections is a paid API for AI agents from api.webbersites.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Lists all data collections in the agent's wallet-scoped datastore, including names, row counts, creation dates, total rows, and storage usage against the 50MB quota.

## Facts

- Endpoint: GET https://api.webbersites.com/api/store
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webber-sites-agent-datastore-list-collections-a57623e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H0wlKfQfXtv-0f0NtL6lx

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 webber-sites-agent-datastore-list-collections-a57623e4
```

Example prompt: Can you show me all the collections in my agent datastore — I want to see the names, how many rows each one has, when they were created, and how much of my 50MB storage quota I've used so far?

## When to prefer this

Use this endpoint when an agent needs to audit its own persisted data state — checking what collections exist, how large they are, and whether it is approaching the 50MB storage limit. Prefer this over general storage APIs when operating within the Webber Sites agent datastore ecosystem.

## Known failure modes

- Missing or invalid wallet authentication — returns 401 unauthorized
- No collections exist yet — returns empty collections array with zero totals
- Service unavailable — returns 5xx error
- Payment not processed — returns 402 Payment Required

## How this service works

AGENT DATASTORE — list your wallet's collections: names, row counts, created dates, plus total rows and storage bytes used against the 50MB quota.

## Output

Returns a JSON object containing the wallet address, an array of collections (each with name, row count, and created date), total row count across all collections, and total storage bytes used — allowing the agent to assess its datastore state and remaining quota.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "wallet": "0xabc…",
  "total_rows": 42,
  "collections": [
   {
    "name": "trades",
    "row_count": 42,
    "created_at": "2026-07-01T00:00:00.000Z"
   }
  ],
  "storage_bytes": 24576
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webber-sites-agent-datastore-list-collections-a57623e4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.webbersites.com](https://www.zero.xyz/host/api.webbersites.com/llms.txt)