ephemeris
https://ephemeris.cascade.industries
Registry code: fb47b2eaa8d6df12
Ephemeris forecasts numeric time series with a panel of zero-shot foundation models (Chronos-2, TimesFM 2.5, Toto 2, TiRex-2, IBM Granite PatchTST-FM and FlowState). Nothing is trained; send history, get quantile forecasts back. Use it whenever the user wants to predict, project or forecast a numeric series: sales, demand, inventory, web traffic, signups, revenue, energy load, prices, sensor readings, infrastructure metrics.
Workflow:
- endpoint
- https://ephemeris.cascade.industries/api/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ephemeris live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is ephemeris free to use?
- No — it asks for a key or a login before it will serve.
- What tools does ephemeris have?
- 4 tools: forecast, list_models, get_balance, get_usage.
- Is ephemeris safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
forecast auth-required never probed
Forecast, predict or project one or more numeric time series (sales, demand, traffic, load, prices, metrics, sensor data) with prediction intervals, using Ephemeris' panel of zero-shot foundation models. Mode ensemble is the most accurate: it is level with the top of the TIME benchmark and scores better on GIFT-Eval than any single model in the panel. Returns structured JSON: `forecasts` (one entry per input series, quantile-keyed arrays) and `meta` with the request id, models used, the served weight revision per model, and the credits charged and remaining. Spends credits on every successful call.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "mode", "series" ], "properties": { "mode": { "enum": [ "route", "ensemble", "explicit" ], "type": "string", "description": "\"route\": Ephemeris picks the best model for the data, falling back to a small ensemble if it fails. \"ensemble\": run all compatible models and blend them; best calibration, highest cost. \"explicit\": run the single model named in `model`." }, "model": { "type": "string", "minLength": 1, "description": "Required when mode is \"explicit\". Must be a name returned by list_models." }, "top_k": { "type": "integer", "maximum": 16, "minimum": 1, "description": "Ensemble only: cap on how many models participate." }, "series": { "type": "array", "items": { "type": "object", "required": [ "values" ], "properties": { "freq": { "type": "string", "minLength": 1, "description": "Pandas-style sampling frequency such as \"H\", \"D\", \"W\", \"15min\" or \"M\". Improves routing and seasonal handling; omit if unknown." }, "values": { "anyOf": [ { "type": "array", "items": { "type": "number" }, "minItems": 1 }, { "type": "array", "items": { "type": "array", "items": { "type": "number" }, "minItems": 1 }, "minItems": 1 } ], "description": "Observed history, oldest first. A flat number array is one univariate series. A nested array is one multivariate series with one inner array per variate, all the same length." }, "covariates": { "type": "object", "required": [ "past" ], "properties": { "past": { "type": "object", "description": "Named historical channels, each the same length as the series context.", "propertyNames": { "type": "string" }, "additionalProperties": { "type": "array", "items": { "type": "number" } } }, "future": { "type": "object", "description": "Known-future channels, each exactly `horizon` long. Every future channel must also appear in `past`.", "propertyNames": { "type": "string" }, "additionalProperties": { "type": "array", "items": { "type": "number" } } } }, "description": "Optional exogenous covariates. Only models with `covariates: true` in list_models can use them. In route and ensemble mode the panel narrows to those models; in explicit mode, naming a model without covariate support is an error." } } }, "maxItems": 64, "minItems": 1, "description": "One to 64 series forecast in one request. All share horizon and quantiles." }, "combine": { "enum": [ "mixture", "vincentize" ], "type": "string", "description": "Ensemble only. \"mixture\" averages the predictive distributions (default); \"vincentize\" averages the quantiles." }, "horizon": { "type": "integer", "maximum": 4096, "minimum": 1, "description": "Number of future steps to forecast, 1 to 4096. Defaults to 64. Some models stop short of this (max_horizon in list_models): route and ensemble skip them, explicit mode rejects the request." }, "quantiles": { "type": "array", "items": { "type": "number", "exclusiveMaximum": 1, "exclusiveMinimum": 0 }, "maxItems": 21, "description": "Up to 21 quantile levels strictly between 0 and 1, for example [0.1, 0.5, 0.9]. The response keys forecasts by these as decimal strings." }, "context_len": { "type": "integer", "maximum": 16384, "minimum": 1, "description": "Most recent points per variate to feed the model and bill for, 1 to 16384. Defaults to 256. Values beyond the model's context cap are truncated at the cap." }, "idempotency_key": { "type": "string", "pattern": "^[A-Za-z0-9._:-]{8,128}$", "description": "Client-chosen key, 8 to 128 characters of letters, numbers, dot, underscore, colon or hyphen. A retry with the same key and identical body replays the stored result without charging again." } } }arguments 142 lineslist_models auth-required 1h ago
Discover the model panel: each model's availability right now (healthy), capabilities (multivariate, covariates, max_horizon, auto_max_horizon), its weight in an ensemble at each horizon, pinned and actually served weight revision, price per thousand series-slots in millicredits and maximum billable context. Call this before using forecast in explicit mode; the deployed panel can differ from any documentation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_balance auth-required 1h ago
Return the account's spendable credit balance in millicredits, excluding credits reserved by in-progress forecasts. 1000 millicredits equal one credit.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_usage auth-required 1h ago
Return the account's forecast request log, newest first, with the mode, models used, series count, horizon, credits estimated and settled, HTTP status and latency of each request.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 200, "minimum": 1, "description": "Rows per page, 1 to 200. Defaults to 50." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Rows to skip. Use `pagination.next_offset` from the previous page." } } }arguments 18 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfb47b2eaa8d6df12.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fb47b2eaa8d6df12/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fb47b2eaa8d6df12?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.