Choose and call the right model for a task through one routing layer. Use it to compare model outputs, switch providers, and run text or multimodal generation workflows.
Use the AIsa AIsa LLM Router skill for my agent. Review https://aisa.one/docs/agent-skills/llm-router and the endpoint list on https://aisa.one/skills/llm-router for capabilities, authentication, pricing, and safety guidance. Configure AIsa API access with AISA_API_KEY. Start with one read-only task, summarize which endpoint you would use, and ask for confirmation before any write, posting, or account-changing action.
API declarations from Docs dcd2a39d6028c66ea61c1154d26d945cd58aa8f4, contract c1d661786e3754a4c0685d969a8a906b3bf891298c423134bd5d3e2f1f9c4732. Prices are published references; quote the actual request for your account.
This concerns the definitions shown here, not Runtime availability. No request schema or price is inferred.
POST /v1/models/{model}:generateContent: No matching request definition in this formal contractPOST /v1/models/gemini-2.0-flash:generateContent: No matching request definition in this formal contractPublished default-request reference, not an account quote. Public reference only; authenticate and quote the actual request for account pricing.
Some response definitions are incomplete; consult the formal API reference.
Formal API referenceRoute this coding task to a strong model and explain the choice.
Compare answers from GPT, Claude, Gemini, and Qwen for the same prompt.
Switch a workflow from one model provider to another through AIsa.AISA_API_KEYUse the Skill.md tab for complete setup details, requirements, and operational guidance from the source skill.