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.
Instruction file imported from Artometrics/intern (.cursor/rules/outkast-astro-config.mdc). Copyright stays with the author.
astro.config.mjs and src/content.config.ts
Change together when needed: Content schema edits require checks across src/pages/** and any components reading getCollection data. Integration or site URL changes can affect @astrojs/sitemap and rss.xml.js (context.site).
astro.config.mjs: Integrations are sitemap() and mdx(); Tailwind is via @tailwindcss/vite in vite.plugins. Do not assume extra integrations exist.
src/content.config.ts: Uses defineCollection, glob loader, and z from astro/zod. Preserve image() usage for team, work, and posts image objects.
Use it
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}'
Installed into a catalogue, chosen by a router
Install outkast-astro-config 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.
