Support
Ask the assistant or browse the FAQ. Email support@solorouter.io if you need a human.
-
What error code do I get on bad arguments? agent
JSON-RPC error code -32602 (Invalid params). The validation runs against `mcp_registry.tools_schema` before any upstream call. -
How many tools come back from discover? agent
Top-N where N = DISCOVERY_TOP_N (default 8). The ranked, filtered, healthy subset only. -
Is there rate limiting? agent
Cloudflare-level abuse protection only. There is no per-session quota — agents are first-class free citizens. -
Do I need an API key as an agent? agent
No. The agent path is unauthenticated and free. Provider credentials are injected server-side by the proxy and never exposed. -
How does an agent connect? agent
POST /mcp/session to get a session_id, then send JSON-RPC requests to /mcp with header `mcp-session-id: <id>`. Initial manifest exposes only `discover_tools(intent)`. -
What is `discover_tools(intent)`? agent
A meta-tool. You pass a natural-language intent; the router runs a semantic search against the registry, persists the matched tools in your session state, and emits notifications/tools/list_changed. -
What happens on `tools/call`? agent
The router validates arguments against the provider's `tools_schema` (JSON Schema), then proxies the call with provider auth headers injected server-side. Failure to validate returns JSON-RPC -32602 and is logged as `validation_failed` — the upstream is never hit. -
Why does my agent only see one tool at first? agent
By design. The initial session manifest exposes only `discover_tools`. Once you call it with your intent, the matching tools become visible via `tools/list`. We never dump the entire registry up front. -
How are tools ranked? agent
Composite score: semantic similarity × tier_boost × trust_boost. Featured > priority > free for tier; audited + healthy + good historical success rate for trust. -
Can I keep a session alive forever? agent
No. KV TTL is bounded; reauthor when expired by issuing a new POST /mcp/session. -
Can I filter discovery by category? agent
Yes. Both the agent meta-tool and the public REST discovery endpoint accept category and tag filters in addition to the intent string. -
How long does a session last? agent
Default 3600 seconds (1 hour), configured via SESSION_TTL_SECONDS. Session state lives in Cloudflare KV. -
How does provider auth work? auth
Supabase Auth. Magic-link email or OAuth (GitHub/Google). Sessions are SSR cookies; the router never sees provider credentials. -
I forgot which email I signed up with. auth
Try the OAuth providers you typically use, then magic-link with each candidate email. We cannot disclose which email owns an account. -
Can I change my account email? auth
Use the Supabase-hosted email change flow from your account page. The change requires confirmation from the old address. -
Can I delete my account? auth
Yes — request deletion via support. All owned MCPs cascade-delete; intent logs survive with `mcp_id_assigned` set to null. -
I get -32602 Invalid Params — why? errors
Your `tools/call` arguments did not match the provider's `inputSchema`. Fix the arguments; the upstream MCP was never hit. -
My MCP is in `degraded` state — why? errors
The last passive or active probe returned 5xx OR took longer than 3000ms. Check your endpoint health; recovery is automatic after 5 consecutive healthy probes. -
I get -32601 Method Not Found — why? errors
The method name is not implemented. The router supports the MCP methods (`tools/list`, `tools/call`, plus discovery meta-tools). -
I get -32600 Invalid Request — why? errors
The body is not valid JSON-RPC 2.0 (missing `jsonrpc:"2.0"` or `method` field). -
I see "session not found or expired" — why? errors
Your `mcp-session-id` was never created or has aged past SESSION_TTL_SECONDS. Call POST /mcp/session again. -
Is the source code open? general
The router is a thin proxy; provider integrations are private. Public docs and the discovery API are open. Contact us for source access. -
What does "chameleonic router" mean? general
The router has no permanently-installed tools. On each session it discovers and exposes only the third-party MCP tools that match the agent's intent, so its surface adapts to the request. -
What is SOLO ROUTER? general
SOLO ROUTER is a chameleonic MCP routing infrastructure for the AI agent economy. It exposes an MCP-compatible JSON-RPC endpoint with no fixed toolset — tools are dynamically selected from a Supabase-backed registry per request and proxied to third-party MCP servers. -
What is MCP? general
Model Context Protocol — Anthropic's open spec for letting LLM agents call external tools over JSON-RPC. SOLO ROUTER speaks MCP natively. -
What are the health states? health
`healthy`, `degraded`, `down`. Default is `healthy`. A 5xx response or latency over HEALTH_LATENCY_THRESHOLD_MS (default 3000ms) instantly marks `degraded` and zeroes trust_boost. -
How long is health data kept? health
7 days. Beyond that, `prune_mcp_health` deletes old rows. -
How does an MCP recover? health
After HEALTH_RECOVERY_OK (default 5) consecutive healthy responses, state resets to `healthy` and trust_boost defaults restore. -
Is health checked passively or actively? health
Both. Every proxied call feeds `mcp_health` (passive). A scheduled worker pings every 5 minutes (active). -
When does an MCP get marked `down`? health
After HEALTH_DOWN_FAILURES (default 3) consecutive active-ping failures. Down MCPs are excluded from discovery entirely. -
Where can I see my MCP's health? health
Provider dashboard, per-MCP. Public discovery surfaces only the current `health_state`, not historical latency. -
Where is the project hosted? infra
Cloudflare Workers (router) + Supabase (registry, auth, intent logs). Both stay strictly inside their free tiers. -
Where do I see trends? intent
The public dashboard at /discover (and the trend section on the landing page) reads from the anonymized view. -
Is my agent's query private? intent
Raw queries are stored. Public consumption is via an anonymized materialized view (`public_intent_trends`). Raw access requires service-role. -
Can I opt out of logging? intent
No — logging is the product. If you cannot accept that, do not use the router. -
What is intent logging? intent
Every request — raw query, semantic embedding, target MCP, outcome — is persisted to `intent_logs`. We mine demand patterns from this dataset; that is the product's long-term moat. -
Where is the company based? misc
Solo Tech Solutions, Co-operative Republic of Guyana. -
How do I report abuse? misc
Use the support chat or email support@solorouter.io. Include the offending MCP id or session_id. -
How do I subscribe to status updates? misc
RSS feed at /rss.xml. Provider-impacting incidents are also emailed to verified owners. -
Do you have an SLA? misc
No paid SLA on the free tier. Featured providers receive priority response on incidents. -
How do I contact a human? misc
Use this support chat — it is AI-assisted but escalates to a human when the model is unsure or you ask for a person. -
Can I self-host SOLO ROUTER? misc
Not officially. The codebase assumes Cloudflare Workers + Supabase. Reach out if you have a strong use case. -
What status flow does a payment go through? payments
`waiting` → `confirming` → `confirmed` → `finished`. Or terminal: `failed` / `expired`. Only `finished` triggers entitlement. -
Which coins are accepted? payments
Whatever NOWPayments supports — BTC, ETH, USDT, USDC, LTC, SOL, and many more. You pick at the hosted checkout. -
Why crypto only? payments
NOWPayments lets us accept funds without ever touching them — funds go straight to our wallet, no card processor, no chargebacks. Keeps infra cost zero and the legal surface small. -
How do I know my payment was applied? payments
When NOWPayments sends a HMAC-verified `finished` IPN, the worker calls apply_payment_entitlement and your dashboard windows update. Allow a few minutes for confirmations. -
I paid but nothing changed in my dashboard. payments
Check the payment status in your NOWPayments invoice. If it is `finished` and the dashboard still does not reflect it after 15 minutes, contact support with your `nowpayments_payment_id`. -
Is the IPN really verified? payments
Yes. We HMAC-verify with NOWPAYMENTS_IPN_SECRET against the raw body. Optional IP allow-list adds defense in depth. Redirect URLs alone never mutate state. -
What if I close the checkout tab? payments
Your invoice stays valid for the on-chain window NOWPayments quotes. Re-open the email/link or buy again — duplicate IPNs are idempotent on `nowpayments_payment_id`. -
Is SOLO ROUTER free for AI agents? pricing
Yes. Agents never pay and never authenticate. Sessions are ephemeral and created via POST /mcp/session. -
Do products auto-renew? pricing
No. Each purchase extends the window by 30 days. You manually re-buy to extend further. -
What does "Priority" cost and include? pricing
$9/month. Boosts your tier_boost in ranking above free listings. Window tracked via `mcp_partners.priority_until`. -
What does "Audit" cost and include? pricing
Audits are hybrid by default. Behavioral phase always runs: black-box probes against your endpoint_url for schema honesty, error handling, prompt-injection surface, latency, and header leakage. If you provide a source repo URL at checkout, the reviewer also reads code for secret handling, dependency CVEs, and auth correctness. Behavioral-only and source-only scopes are also selectable. -
What does "Featured" cost and include? pricing
$9/month. Top tier_boost — ranks above priority listings — plus a featured badge on the discovery explorer. Window tracked via `mcp_partners.featured_until`. -
Are prices per MCP or per account? pricing
Audit is per MCP. Priority and Featured are tier flags on `mcp_partners` keyed by user_id; the boost applies to all your MCPs while the window is active. -
Can I cancel and refund? pricing
Crypto payments via NOWPayments are non-reversible once confirmed on-chain. We do not issue refunds. Confirm before paying. -
Can I stack Priority and Featured? pricing
Featured supersedes Priority — you pay only for Featured. Audit is independent and stacks with both. -
Who pays then? pricing
Only MCP providers pay, and always optionally — for audits, priority placement, or featured slots. Routing itself is free. -
Can the repo I share be private? pricing
Yes. Provide either a public URL or instructions for read-only access (GitHub team invite, deploy key, or a signed zip link). Add details in the access notes box at checkout. -
How long does an audit take? pricing
Behavioral: usually under a day. Hybrid/source: 2-5 business days depending on repo size. We email the report URL when it is ready. -
What does the audit report include? pricing
A markdown report with: scope (behavioral / hybrid / source), probe transcript, findings categorized by severity, recommendations, and the audited-until window. Stored under audits.report_url for both you and the reviewer. -
Do you need source code for an audit? pricing
No — behavioral audits are the default and require no code access. They probe your live endpoint. Hybrid (recommended) adds source review if you supply a repo URL or invite at checkout. Source-only is available too. -
What happens if I do not give source access? pricing
Audit scope falls back to behavioral. We probe your endpoint as a black box: schema honesty, error handling, prompt-injection resistance, latency, header leakage. Findings still produce a report and the audited badge. -
What data do you store about providers? privacy
Auth identity (Supabase), MCP listings you create, your `mcp_partners` window timestamps, and payment records keyed by `nowpayments_payment_id`. -
Where is data stored? privacy
Supabase (Postgres) for relational data and embeddings. Cloudflare KV for ephemeral session state. No third-party analytics on the agent path. -
What data do you store about agents? privacy
Per request: session_id (random, ephemeral), raw_query, intent_embedding, mcp_id_assigned, success_status, timestamp. No agent identity beyond the session_id. -
Are you GDPR compliant? privacy
Provider data is handled per Supabase's GDPR posture. Agent data is identifierless beyond an ephemeral session_id. Deletion requests honored on request. -
Why must I provide tools_schema? provider
Without it the router cannot validate arguments and would have to forward unsafe payloads. Schemaless listings are rejected. -
Can I have multiple MCPs under one account? provider
Yes. The dashboard lists all MCPs you own (filtered by `owner_user_id` via RLS). -
How long does verification take? provider
Usually under 5 minutes. The active-ping cron runs every 5 min; verification is one of the jobs. -
How do I list my MCP? provider
Sign in at /login (email or GitHub/Google), then go to /submit. Fill name, description, endpoint URL, category, tags, and tools_schema. Listing starts as `pending` until our verification pings your endpoint. -
What is `tools_schema`? provider
A JSONB column on `mcp_registry` holding MCP tool definitions with full `inputSchema`. It is the source of truth used to validate tools/call arguments before proxying. -
Can I delete my MCP? provider
Yes. Deletion cascades to dependent rows (mcp_health, intent_logs.mcp_id_assigned is set to null). Past intent logs survive anonymized. -
How do I update my listing? provider
Edit it in the provider dashboard. Any change to name/description/tags/category triggers re-embedding via Postgres trigger. -
What does verification do? provider
A worker pings your endpoint and checks the JSON-RPC handshake. Three consecutive successes flip status to `active`; failures keep you in `pending` and surface a reason in your dashboard. -
How do I disable my MCP temporarily? provider
Set status to `disabled` from the dashboard. It is removed from discovery immediately.
No FAQs match that filter. Try the chat instead.