# CoinStats Portfolio Sync Status

> CoinStats Portfolio Sync Status is a paid API for AI agents from x402.coinstats.app, paid per call via x402, $0.001/call, status down (last checked 2026-09-15).

Returns the sync status of a shared CoinStats portfolio, indicating whether the portfolio data is up-to-date or pending refresh

## Facts

- Endpoint: POST https://x402.coinstats.app/portfolio/status
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-coinstats-app-8c2f9d6b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C9ArhcuDzlYmU-Tg5D5fH

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 x402-coinstats-app-8c2f9d6b -d '<json body>'
```

Example prompt: Check whether my CoinStats shared portfolio is fully synced and up to date — here's my sharetoken from my Degen-plan account.

## When to prefer this

Use this endpoint when you need to verify whether a CoinStats shared portfolio's data is current before relying on its balance or value data. Ideal for polling before fetching portfolio snapshots or charts to ensure you're working with fresh data. Requires a Degen-plan CoinStats sharetoken.

## Known failure modes

- Missing or invalid sharetoken header returns unauthorized error
- Expired or revoked sharetoken returns 401/403
- Portfolio not found returns 404
- CoinStats Degen plan required — free-tier sharetokens may be rejected
- Network timeout if CoinStats backend is slow to respond

## How this service works

Portfolio sync status

## Output

Returns the current sync status of the specified shared portfolio, indicating whether portfolio data has been successfully synchronized, is in progress, or has encountered an error, potentially including a timestamp of the last successful sync.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "type"
 ],
 "properties": {
  "type": {
   "enum": [
    "24h",
    "1w",
    "1m",
    "3m",
    "6m",
    "1y",
    "all"
   ],
   "type": "string",
   "description": "Time period for the data"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-coinstats-app-8c2f9d6b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.coinstats.app](https://www.zero.xyz/host/x402.coinstats.app/llms.txt)