Endpoint
api.robinx.io/agent/features
One call returns the token-level feature row for a Robinhood Chain token, shaped for a trading agent to fold into its own model: immutable launch facts, current activity (swaps/volume/traders/is_real, plus the exact is_real crossing block, recovered back to chain genesis), the deployer's current track record, the latest price/FDV quote with its real observation time, and observed social measurements (exact mention counts, distinct accounts, first mention, 24h velocity, how many mentioning accounts are MEASURED callers, best early-rate, mutual-follow cluster share, the k-gated Telegram first-sighting record, and the fomo cohort count — how many tracked public fomo traders our live tape recorded on the token; counted, never identified). Response is split by epistemic status — current_state carries no history and must not be joined to a past timestamp; observed sits on an immutable capture clock. We publish inputs, never predictions: no score, no recommendation, no expected return.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 5h ago | 402 | 262 ms | exact eip155:8453 |
0xA13d…0599 | 0.030000 | clean |
| 4d ago | 402 | 1055 ms | exact eip155:8453 |
0xA13d…0599 | 0.030000 | clean |
| 4d ago | 402 | 204 ms | exact eip155:8453 |
0xA13d…0599 | 0.030000 | clean |
Reference
| URL | https://api.robinx.io/agent/features |
| Sources | bazaar well-known |
| Recipient per catalogue | 0xA13d363AeCCCF878Ec64f6eB687Eb4A771FB0599 |
| Price per catalogue | 0.030000 |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.