Integration recipes
Connect your provider or framework at an explicit application boundary.
Use the SDK to check input before a protected operation and buffered output before release. A recipe is an implementation starting point; live verification is listed separately in the support matrix.
Integration names identify services you can connect from your application. They are not a list of Nyraxis’s internal detector engines or active subprocessors. Review hosted service providers and your selected processing destinations separately.
Start with a verified journey
Real LangGraph agent
Reusable Python gate
Reusable Node gate
Choose a provider or framework
- OpenAI
- Anthropic
- LangChain
- LangGraph agent journey
- LlamaIndex
- Vercel AI SDK
- CrewAI
- AutoGen
- Semantic Kernel
- Haystack
- DSPy
- Mistral AI
- Cohere
- Google Gemini
- AWS Bedrock
- Azure OpenAI
- Groq
- Together AI
- Fireworks AI
- Replicate
- Ollama
- Express
- Flask
- Django
The reusable helpers default to the docs-integration agent. Set NYRAXIS_AGENT_NAME to select another configured agent without editing the helper.
Acceptance for your application
Configure the correct agent policy scope, pin provider versions, test safe and blocked input/output, simulate an unavailable check, and count actual provider requests. Add permissions before tools with side effects. A trace receipt, recipe or successful import does not establish enforcement for every call in a framework.