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 41103e660218ed95a09c8a90686301604497d918, contract 564fc5afa483600d6bea4cb99f3496c83dfce8b310aa05e382a68d60670dd1b9. 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.