A stable HTTP interface to Velocity’s trend and market intelligence. Authenticate with a vel_* Bearer key, call two endpoints, and get scored signals as clean JSON — CORS-enabled, quota-metered, ready for any backend or agent.
https://velocity.andiamo.techAll public endpoints live under /api/v1/. Responses are JSON and include CORS headers.
Authorization: Bearer vel_…Mint keys in the Agent Hub. Shown once, stored as a SHA-256 hash. The REST API requires a Starter plan or above.
# Active security trends with a velocity score >= 50
curl -H "Authorization: Bearer vel_your_api_key" \
"https://velocity.andiamo.tech/api/v1/trends?category=security&minScore=50&limit=10"
# Lightweight pulse snapshot for crypto
curl -H "Authorization: Bearer vel_your_api_key" \
"https://velocity.andiamo.tech/api/v1/pulse?category=crypto"Both require a vel_* key, are CORS-enabled, and count against your daily quota.
/api/v1/trendsActive trends sorted by velocity score, with recent data points and sources.
| Param | Type | Default | Description |
|---|---|---|---|
category | string | all | Filter by category, e.g. security, crypto, market. |
limit | number | 20 | Max results (1–100). |
minScore | number | 0 | Minimum velocity score (0–100 internal scale). |
/api/v1/pulseLightweight snapshot — the latest data point per tracked item. Ideal for dashboards.
| Param | Type | Default | Description |
|---|---|---|---|
category | string | all | Filter by category. |
status | string | active | Item status filter. |
limit | number | 50 | Max results. |
{
"data": [
{
"id": "crypto-bitcoin",
"title": "BTC Price",
"description": "Bitcoin cryptocurrency price tracking",
"category": "crypto",
"subcategory": null,
"velocityScore": 78,
"velocityState": "rising",
"sourceCount": 5,
"dataPoints": [
{ "timestamp": "2026-06-10T18:00:00.000Z", "score": 78, "granularity": "five_min" }
],
"sources": [
{ "id": "…", "title": "BTC: $68,421 (+2.3%)", "url": "https://…", "publishedAt": "…" }
],
"firstSeen": "2026-05-15T…",
"lastUpdated": "2026-06-10T…"
}
],
"meta": {
"total": 20,
"limit": 20,
"category": "all",
"minScore": 0,
"timestamp": "2026-06-10T18:00:00.000Z"
}
}The owning user’s current subscription tier sets the quota — upgrades take effect without rotating keys.
| Plan | REST quota | Notes |
|---|---|---|
| Free | — | No REST access (403). View trends in-app + use most MCP tools. |
| Starter | 24 / day | Minimum tier for the REST API. |
| Pro | 500 / day | Analyst / agent-builder tier. |
| Unlimited | 5,000 / day | Real-time data feed territory. |
| Startup | 10,000 / day | Per seat; team plan. |
| Enterprise | Unlimited | Team plan. |
Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (a Unix epoch-seconds reset time). When the daily quota is exhausted, the API returns 429 with a Retry-After header. Quotas reset at the start of each UTC day.
Errors return a JSON body with an error key and a human-readable message.
| Status | error | Meaning |
|---|---|---|
| 400 | bad_request | Validation error in query params. |
| 401 | unauthorized | Missing or invalid vel_* key. |
| 403 | tier_too_low_for_api_access | Free-tier key — REST API requires Starter or above. |
| 429 | quota_exceeded | Daily quota exhausted. Includes Retry-After. |
| 500 | internal_error | Server error — safe to retry with backoff. |
If an AI agent is the consumer, the MCP server exposes 14 read-only tools over JSON-RPC — search, intel briefs, momentum checks, CVE lookups, threat-actor attribution, and tech-stack alert subscriptions — using the same vel_* keys. See the AI agents use case for concrete playbooks, or the docs hub for the full picture.
Create an account, upgrade to Starter or above, and mint a key to make your first call.