synap
Registry code: c6d1514b4a803e26
Synap is Linkrra's OpenAI-compatible inference API for open models (https://synap402.com). synap_list_models, synap_get_model and synap_estimate_cost are free, read-only and need no key — use them to pick a model and price a job. synap_chat_completion runs a model and bills the Synap API key sent as the Authorization: Bearer header on this MCP connection; without a key it returns an error and spends nothing. Use model "synap-v1" to let Synap route to the cheapest model that can do the job.
- endpoint
- https://pool.linkrra.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is synap live?
- Yes — it answered the hub's last check (checked 7m ago). It answered 100% of checks over the last 30 days.
- Is synap free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does synap have?
- 4 tools: synap_get_model, synap_estimate_cost, synap_chat_completion, synap_list_models.
- Is synap 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 98.2%· all time 98.2%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get a chat completion from an llm
- list available llm models
- takes → gives
- text → text, data
- tools
- 2 reads
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-11
concentrated, shared-payto
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.
synap_list_models reads open 10h ago
List the models Synap serves right now, each with its price per million tokens, context window and what it is good at. Use this to choose a model id before calling synap_chat_completion, or to compare prices. Free, read-only, no API key needed, and safe to call repeatedly; the list is live, so models can appear or go between calls. Returns {"object":"list","count":N,"data":[{id,name,capability,tier,context_tokens,max_output_tokens,pricing,data_policy}]}; pricing is USD per million prompt and completion tokens and is absent for the auto-routing ids ("synap-v1"), which bill at the price of the model they route to. For every field of one model use synap_get_model.
{ "type": "object", "properties": { "query": { "type": "string", "description": "Optional case-insensitive filter matched against model id, name and capability, e.g. \"coder\", \"qwen\" or \"vision\". Omit to list everything." } } }arguments 9 linessynap_get_model unknown 10h ago
Return the complete catalogue record for one Synap model: pricing, context and output limits, supported parameters, quantisation, data-retention policy and readiness. Use this after synap_list_models when you need details the summary leaves out. Free, read-only and needs no API key. Returns the raw model object, or an error naming the id if Synap does not serve it.
{ "type": "object", "required": [ "model" ], "properties": { "model": { "type": "string", "description": "Model id exactly as returned by synap_list_models." } } }arguments 12 linessynap_estimate_cost unknown 10h ago
Work out what a chat completion would cost on Synap from token counts, using the live price list. Use this before synap_chat_completion when budget matters, or to compare models for a job. Free, read-only, needs no API key and runs no model. Returns {model, prompt_tokens, completion_tokens, prompt_usd, completion_usd, total_usd, pricing}. It is an estimate: the real charge uses the token counts the model reports afterwards. Auto-routing ids such as "synap-v1" have no fixed price and return an error saying so.
{ "type": "object", "required": [ "model", "prompt_tokens" ], "properties": { "model": { "type": "string", "description": "Model id exactly as returned by synap_list_models." }, "prompt_tokens": { "type": "integer", "minimum": 0, "description": "Tokens you will send (system + conversation). Roughly 4 characters of English per token." }, "completion_tokens": { "type": "integer", "minimum": 0, "description": "Tokens you expect back. Use your max_tokens for a worst case. Defaults to 0." } } }arguments 23 linessynap_chat_completion reads unknown never probed
Send a conversation to a model on Synap, Linkrra's OpenAI-compatible inference API, and get the model's reply. Use this when you need text generated, code written or a question answered by one of the open models Synap serves. This is the only tool here that costs money: it bills prompt and completion tokens to the Synap API key supplied as the Authorization: Bearer header on the MCP connection. With no key it returns an error and nothing is spent; a key with no balance returns insufficient_credits. Call synap_estimate_cost first if the price matters. Returns the standard OpenAI chat.completion JSON (choices[0].message.content holds the reply, usage holds token counts). The call is not streamed and keeps no memory between calls — send the full message history each time.
{ "type": "object", "required": [ "model", "messages" ], "properties": { "model": { "type": "string", "description": "Model id exactly as returned by synap_list_models, e.g. \"qwen3-coder-30b\". Use \"synap-v1\" to let Synap pick the cheapest model that can handle the request." }, "messages": { "type": "array", "items": { "type": "object", "required": [ "role", "content" ], "properties": { "role": { "enum": [ "system", "user", "assistant" ], "type": "string", "description": "Who wrote the message: system (instructions), user, or assistant (an earlier model reply)." }, "content": { "type": "string", "description": "The message text." } } }, "minItems": 1, "description": "The conversation so far, oldest first. The last message is normally the user turn to answer." }, "max_tokens": { "type": "integer", "minimum": 1, "description": "Upper limit on tokens generated in the reply. Omit to use the model default; lower it to cap cost." }, "temperature": { "type": "number", "maximum": 2, "minimum": 0, "description": "Sampling randomness, 0 to 2. Lower is more deterministic. Omit to use the model default." } } }arguments 51 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 idc6d1514b4a803e26.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6d1514b4a803e26/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c6d1514b4a803e26?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.