AGENT-TO-AGENT (A2A) INTEROPERABILITY AND QUALITY
Agent-to-agent communication, without framework lock-in. Improve the quality of the agents you already run, make them callable by any other agent, and get them discovered.
curl -fsSL https://superoptix.ai/install.sh | shADAPT · SERVE · MEASURE · OPTIMIZE
Once declared, automatic pipelines. Write once, compile everywhere, optimize every layer.
Write your agent as a SuperSpec YAML specification. Define behavior, tools, and goals once.
Generate native pipelines for DSPy, OpenAI, Claude SDK, CrewAI, Google ADK, Pydantic AI, DeepAgents, or Microsoft.
Run the BDD specification, then write an Agent Quality Record stating what was measured, what the agent was permitted to do, and who accepted the result.
GEPA optimizes across prompts, RAG, memory and context. Measure how often other agents route to yours, then improve the Agent Card until they do.
One command reads your agent, derives the skills a calling agent would route on, and writes an Agent Card and a conformant server. Your code is not modified.
Point super a2a adapt at an agent you already run. SuperOptiX reads its structure and writes an A2A 1.0 Agent Card and server. Your code is not modified.
SuperOptiX now supports core A2A v1 interoperability so agents built with SuperOptiX can be exposed over A2A and can also call external A2A agents.
Explore A2A supportZero failures against the official Technology Compatibility Kit, 73 of 73 MUST requirements exercised on the conformance harness. A live agent runs at a2a.superoptix.ai with its Agent Card published on this domain.
Native generation flows across DSPy, Pydantic AI, Google ADK, OpenAI Agents SDK, DeepAgents, CrewAI, Claude Agent SDK, and Microsoft Agent Framework.
Generated pipelines across all supported frameworks are now significantly simpler. The default output is readable and runnable, without heavy runtime scaffolding.
Optimization and evaluation logic now lives behind --optimize, so base pipelines stay focused and clean.
curl -fsSL https://superoptix.ai/install.sh | shsuper init swecd swesuper agent pull developersuper agent compile developer --framework dspysuper agent run developer --framework dspy --goal "Design a migration strategy"super agent compile developer --framework dspy --optimizesuper agent optimize developer --framework dspy --auto lightFrameworks compete on how an agent is assembled. What happens after it runs is usually left to hand-tuning, with prompts edited by feel and nothing measuring whether the change helped.
Optimization at each layer is what moves an agent from a demo to something worth running in production. SuperOptiX treats that as the whole product, combining published optimizers with our own, across any framework you already run.
Instructions evolve against a scored task set rather than being edited by hand until they look right.
What the agent is given to read, selected and structured so the useful material survives the window.
The steps between input and answer, tuned end to end instead of one component at a time.
Hyperparameters and configuration, moved with the rest of the stack rather than pinned at defaults.
Most teams adapt an agent they already run. Starting fresh is the other road: write one specification and compile it to native code on any of the eight frameworks.
Framework glue code everywhere
Provider-specific logic duplicated
Manual prompt tweaking is endless
Heavy runtime scaffolding
Define intent once in SuperSpec YAML
Generate framework-native pipelines
Optimize with GEPA when ready
Keep code ownership and readability
| Area | Other Frameworks | SuperOptiX |
|---|---|---|
| Pipeline Output | Heavy runtime scaffolding | Minimal, framework-native code |
| Framework Lock-in | Rewrite for each framework | One spec, 8 frameworks |
| Optimization | Manual or framework-specific | Explicit --optimize path with GEPA |
| Code Ownership | Framework abstractions hide logic | Readable, native pipelines you own |
An evaluation reports what passed today. Six months later, when somebody asks what was checked before the agent went live, the answer has to be reconstructed from memory.
One flag writes it down instead: the scenarios the agent was measured against, what it was permitted to do, the measures the run produced, and who accepted the result. The output follows SuperGauge, an open format any implementation can read.
How the record workssuper agent evaluate developer --gauge-out record.yamlsubject:
agent: developer
authority: {sandbox: docker, egress: deny-by-default}
task_set:
manifest_digest: sha256:7d02...
held_out: 2
sealed: true
measures:
- {id: task.completion, value: 0.83, n: 8}
decision:
verdict: holdSuperOptiX compiles a single SuperSpec YAML into framework-native agent pipelines across 8 frameworks. Stay close to each framework's native programming model.

Complex reasoning & research

Simple & fast agents

Anthropic Claude agents
Multi-agent teams
Gemini-native integration
Type-safe agents with MCP

Complex planning & reasoning
Enterprise Azure (legacy)
The Genetic-Pareto (GEPA) optimizer works across all 8 supported frameworks. Enable optimization only when needed with the explicit --optimize path.
We're continuing to expand SuperOptiX
Improved optimization ergonomics and GEPA-focused workflows
Long-running A2A tasks that report back without holding a connection open
Publishing Agent Cards to enterprise agent registries and galleries
Better debugging UX and observability tooling