canonical: https://jentic.com/apis/pharos.watch/pharos # Pharos Watch Pharos API The Pharos API serves stablecoin analytics for peg monitoring, liquidity, risk, and market structure. It returns the tracked stablecoin list with supply, price, peg, and chain distribution, a full analytics dossier per coin such as usdt-tether or usdc-circle, and a chronological feed of depeg, freeze, and score events filterable by severity and time window. Safety Score report cards and history, DEX liquidity scores, mint and burn flows, freeze and blacklist events, yield rankings, chain health scores, reserve composition, and immutable daily dataset snapshots round out the surface. ## For AI agents Read stablecoin peg status, depeg events, Safety Scores, DEX liquidity, mint and burn flows, freeze and blacklist events, yields, and daily snapshots from Pharos. ## Scope Does not trade, custody, mint, or redeem stablecoins, and does not move funds. Use for reading stablecoin peg, risk, flow, and freeze analytics only. ## Capabilities - Pull the current stablecoin list with supply, price, peg, and chain distribution - Retrieve a per-coin analytics dossier, summary, or reserve composition by stablecoinId - Follow historical and active depeg incidents, with a resolution outlook per active depeg - Filter the events feed by type such as depeg.opened, coin, chain, severityFloor, and since and until timestamps - Read Safety Score report cards, safety-score history, and yield rankings for stablecoins - Track freeze and blacklist events by stablecoin symbol, chain, and eventType such as blacklist or destroy - Fetch mint and burn events for a stablecoin with direction, burnType, and minAmount filters ## Use cases ### Stablecoin risk agent through Jentic An AI agent watching a treasury's stablecoin holdings needs grounded peg and risk data before it raises an alarm. Through Jentic the agent searches for 'check for active stablecoin depegs', loads the Pharos depeg events operation with its input schema, and queries active incidents, then reads the per-coin dossier and resolution outlook for any affected coin. The X-API-Key is injected at call time by your own Jentic One instance. Example prompt: Call GET `/api/depeg-events` with active=true, then GET `/api/stablecoin/{stablecoinId}` and GET `/api/depeg-resolver` for each affected coin and summarise the outlook ### Freeze and blacklist surveillance Compliance and on-chain analysts track when issuers freeze or destroy funds at specific addresses. The blacklist operation filters events by stablecoin symbol such as USDC or USDT, chain or chainId, eventType of blacklist, unblacklist, or destroy, and an address substring, with sort and pagination, while the summary operation gives totals and chart data. Example prompt: Call GET `/api/blacklist` with stablecoin=USDT, chainId=tron, eventType=blacklist, and sortDirection=desc, then report the newest affected addresses ### Issuance flow analysis Market analysts read mint and burn activity as a signal of demand for a stablecoin. Aggregate flows cover a lookback window in hours, and the event-level operation lists individual mints and burns for one stablecoin, filterable by direction, burnType such as effective_burn or bridge_burn, chain, and a minimum USD amount. Example prompt: Call GET `/api/mint-burn-events` with stablecoin=usdc-circle, direction=mint, and minAmount=1000000, then compare with GET `/api/mint-burn-flows` for the same coin ### Yield and safety comparison A DeFi researcher choosing a yield-bearing stablecoin wants return and risk side by side. Yield rankings come with safety and benchmark context, yield history is available per coin in best or source mode, and Safety Score history shows how a coin's grade has moved over time. Example prompt: Call GET `/api/yield-rankings` with projection=summary, then GET `/api/safety-score-history-v2` with stablecoin set to the top-ranked coin and days=365 ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/stablecoins` | List stablecoins with supply and peg | | GET | `/api/stablecoin/{stablecoinId}` | Get a per-coin analytics dossier | | GET | `/api/depeg-events` | List depeg incidents | | GET | `/api/events` | Get the typed event feed | | GET | `/api/report-cards/v9` | Get Safety Score report cards | | GET | `/api/blacklist` | List freeze and blacklist events | | GET | `/api/mint-burn-events` | List mint and burn events | | GET | `/api/yield-rankings` | Rank yield-bearing stablecoins | ## Key resources - **Stablecoins** — Tracked coins with supply, price, peg, chain distribution, reserves, and per-coin dossiers - **Depeg and event feed** — Depeg incidents, resolution outlooks, stress signals, and a typed event feed with severity levels - **Safety and liquidity** — Safety Score report cards and history, bluechip ratings, DEX liquidity scores, and redemption backstops - **Flows, freezes, and snapshots** — Mint and burn events, freeze and blacklist events, yields, chain aggregates, digests, and daily snapshots ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 53 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 48 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 36 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/pharos.watch/pharos/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Pharos by hand means requesting a supporter or partner key, sending it in the X-API-Key header on protected routes, and handling both offset and keyset cursor pagination across event feeds. Through Jentic you install once, import Pharos from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Pharos puts the stablecoin id in the URL path on its per-coin routes (`/api/stablecoin/{stablecoinId}`), so a rule can pin your agent to one coin's dossier and reserves. The API is read-only, and you choose the operations it may call, so heavy routes like full daily snapshots are not included unless you add them. - **Credential handling:** Your Pharos API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check for active stablecoin depegs' or 'list USDT freeze events', and Jentic returns the matching Pharos operation with its input schema, including the canonical stablecoin id format, so the agent calls the right endpoint directly. ## Related APIs - **CoinGecko** — Broad crypto prices and market caps across thousands of assets - **CoinAPI Market Data REST API** — Exchange-level trades, quotes, and OHLCV across many venues - **0xArchive API** — Historical and current market data for Hyperliquid and Lighter perpetuals ## FAQ ### What authentication does the Pharos API use? The Pharos API authenticates with an API key in the X-API-Key header (ApiKeyAuth) per its OpenAPI spec, required on its protected public routes. A few routes are free and need no key, including GET `/api/health`, GET `/api/safety-grades`, GET `/api/dependency-graph/v1`, and GET `/api/dependency-scenarios/v1.` Supporter and partner keys are requested from the Pharos API page, and through Jentic the key is stored by your own instance and attached at call time. ### Can I get only active depegs with the Pharos API? Yes. GET `/api/depeg-events` accepts active=true to return only active incidents, and a stablecoin parameter to narrow to one coin. includePending adds incidents still awaiting confirmation, and GET `/api/depeg-resolver` gives a resolution outlook and duration estimate for each active confirmed depeg. ### What are the rate limits for the Pharos API? The OpenAPI spec does not specify request rate limits. Limits depend on whether you hold a supporter or partner key, so check https://pharos.watch/api/ for current access terms before running bulk history pulls. ### Is there a Pharos MCP server? You don't need an MCP server to give your agent Pharos. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the peg, event, and safety operations on demand without loading another server's tool definitions into its context. ### How do I read a stablecoin's dossier through Jentic? Search Jentic for 'get stablecoin analytics', load the GET `/api/stablecoin/{stablecoinId}` operation, and execute it with a canonical Pharos ID such as usdc-circle. For a lighter price and supply snapshot, use the stablecoin summary operation instead. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Pharos API? Yes. Write a rule that allows GET `/api/stablecoin/{stablecoinId}` and GET `/api/stablecoin-reserves/{stablecoinId}` for usdc-circle only, and the agent can read that coin's dossier and reserves while other routes stay outside its allowed set. Every call it makes is logged for review.