Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
ttt-e2e-long-context - Skill - OpenSmartRoute
Skillv1.0.0
ttt-e2e-long-context
Enable long-context modeling via test-time training with meta-learning. Inner loop continues training on context, compressing information into weights rather than KV cache, outer loop optimizes initia
Imported from ADu2021/skillXiv (skills/skillxiv-v0.0.2-claude-opus-4.6/ttt-e2e-long-context/SKILL.md). Install upstream with npx skills add ADu2021/skillXiv --skill ttt-e2e-long-context. Copyright stays with the author (MIT).
Overview
Reformulates long-context as continual learning problem solved at test time.
Core Technique
Meta-Learning for Test Time:
# Inner loop: compress context into weightsfor token in context: gradient = compute_gradient_on_token(model, token) model.weights += gradient # Compress context# Outer loop: optimize initialization# Treat inner loop as differentiable step
Performance
Full-attention quality across context lengths
2.7× faster than attention at 128K
Constant-time inference
References
Test-time meta-learning
Weight compression of context
End-to-end optimization
Use it
Installed into a catalogue, chosen by a router
Install ttt-e2e-long-context and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
When a provider is down or over quota the request moves on; the trace says it did.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
