agentfeed-briefs
Use when an agent needs a short crypto market brief or a perp signal: what changed overnight in BTC, ETH, SOL and HYPE with the one level to watch, which Hyperliquid perps moved unusually, whether funding, liquidations or open interest are abnormal right now, or the signal board and coin signals. Calls AgentFeed over HTTP. Scheduled or unattended runs send one flat signals pass (or a prepaid key) from the AGENTFEED_KEY environment variable, so no payment prompt is needed; attended runs can pay per call with x402. Describes what moved, never what to trade.
AgentFeed briefs
Three short briefs built only from data AgentFeed already collects, and the perp signal routes that sit beside them. Each one gives the judgment (what changed, why it matters, the one level to watch), not a raw number. The text is templates over numbers: no language model, nothing invented. It never says what to trade, and you should not turn it into a trade instruction.
Service: https://x402.ochinimus.app. Every route is a GET and returns JSON. The three briefs take no parameter; the signal routes take the optional ones listed in references/ROUTES.md and in /openapi.json.
When to use which brief
| Brief | Route | Price per call |
|---|---|---|
| Morning brief | GET /api/morning-brief | $0.03 |
| Move alert | GET /api/move-alert | $0.02 |
| Anomaly flag | GET /api/anomaly-flag | $0.02 |
Pick by the question:
- What changed overnight in BTC, ETH, SOL and HYPE, and what is the one level to watch? ->
/api/morning-brief - Which Hyperliquid perps moved unusually, and was it the calendar or unexplained flow? ->
/api/move-alert - Is anything abnormal in funding, liquidations or open interest across the perps right now? ->
/api/anomaly-flag
The same key also reads the perp signal routes (below), so a scheduled run can mix them under one flat price:
| Signal | Route | Price per call |
|---|---|---|
| Market state | GET /api/market-state | $0.02 |
| Perp signal board | GET /api/signal-board | $0.01 |
| Coin signal | GET /api/coin-signal/{coin} | $0.004 |
| Open interest spikes | GET /api/oi-spike-scan | $0.02 |
| Liquidation heatmap | GET /api/liq-heatmap | $0.02 |
- What is the full pre-trade picture for this coin right now? ->
/api/market-state - Which Hyperliquid perps are crowded, squeezing or being liquidated right now? ->
/api/signal-board - What is the positioning, liquidation and cascade picture for one coin right now? ->
/api/coin-signal/{coin} - Where is new leverage piling in? ->
/api/oi-spike-scan - At which price levels did leverage actually get flushed? ->
/api/liq-heatmap
The pass paces each route once per 60 seconds per key. /api/coin-signal/{coin} keeps ONE clock for every coin: to read several coins at once call /api/signal-board?coins=BTC,ETH,SOL.
Pay: choose by how you run
Scheduled, cron or unattended (nobody can approve a payment): use a key. A human or an attended agent buys it once, puts it in the environment variable AGENTFEED_KEY, and every call sends it as the header X-AgentFeed-Key:
curl -s -H "X-AgentFeed-Key: $AGENTFEED_KEY" https://x402.ochinimus.app/api/morning-brief
There is no payment prompt, so a cron run cannot stall on one. Never print the key, never write it into a file you commit, never put it in a URL. If AGENTFEED_KEY is empty, stop and tell the user a key is needed; do not buy one yourself.
A key can be one of three things:
- signals pass (
GET /api/keys/buy-signals-pass, $25 flat, 30 days): one flat key for the briefs and the perp signal routes, good only on/api/morning-brief,/api/move-alert,/api/anomaly-flag,/api/market-state,/api/signal-board,/api/coin-signal/{coin},/api/oi-spike-scan,/api/liq-heatmap, nothing drawn per call, one call per route every 60 seconds per key. Non-refundable, no top-up, a bearer secret: anyone who holds the key uses the pass. - signals day pass (
GET /api/keys/buy-signals-day-pass, $1 flat, 24 hours): one flat key for the briefs and the perp signal routes, good only on/api/morning-brief,/api/move-alert,/api/anomaly-flag,/api/market-state,/api/signal-board,/api/coin-signal/{coin},/api/oi-spike-scan,/api/liq-heatmap, nothing drawn per call, one call per route every 60 seconds per key. Non-refundable, no top-up, a bearer secret: anyone who holds the key uses the pass. - Prepaid pack (
GET /api/keys/buy-1,buy-5,buy-20): a balance; each call draws half the route price (minimum $0.0005). Works on every AgentFeed route.
Both can be bought at https://x402.ochinimus.app/keys in a browser with a Base wallet; the page makes the key in the browser and sends AgentFeed only its hash. A stock x402 client with its default $1 spend cap can buy the $1 day pass as is.
Attended (a person or an x402 client is present): call the route without a key. It answers 402 with the price in the PAYMENT-REQUIRED header (base64 JSON); pay it with any x402 client and repeat the request with a PAYMENT-SIGNATURE header. Buying a key or a pass is a payment: ask the user first.
Try it free first
https://x402.ochinimus.app/api/sample/<route> returns the brief's real response shape for nothing, e.g. https://x402.ochinimus.app/api/sample/morning-brief. The numbers in the three brief samples are generated, not market readings; use them to see the fields and the wording. The signal routes' samples are trimmed captures of real answers.
Reading an answer
The body of every route is { "tool", "data", "paid" }. For the three briefs data is:
headline: one sentence, the most abnormal item. Quote it first.items[]: ranked byabnormality(1.0 means an item just meets its rule). Each haswhat,why_it_matters,numbers,source,as_ofand, when one exists,level_to_watch.sources[]: every part used, withas_ofandage_s.stale_parts[]: parts that were too old or missing. They are left out, never served as fresh. If this is not empty, say which parts are missing.method: the thresholds and the sample sizes. Read it before explaining a number.
Say plainly when items is empty: it is a real answer ("nothing past its rule"), and checked or coins_checked says what was looked at.
Errors
- 503 with
Retry-After: the data behind the brief is stale or missing. You were not charged. Wait the number of seconds and retry once; do not loop. - 429 with
retry_after: a pass answers each brief once per 60 seconds. Wait, do not retry sooner. A 429 is not billed. - 401/403 on a pass: expired, or the key is for other routes. The body names the pass to buy again.
- 402 with a key: the key has no balance (a prepaid pack) or you sent none.
Scheduling
See references/SCHEDULING.md for a cron line, a Hermes Agent job and a Claude Code routine. Facts about the routes, prices and pass terms are in references/ROUTES.md; they are generated from the AgentFeed code and change with it.
- Downloads
- 72All time
- Security audit
- Review
- Last updated
- 3d ago
- Current version
- v0.1.1
- License
- MIT-0
