NIMOS / ENGINES / AgentAPILayer
← THE BUILD SYSTEMAgentAPILayer
THE OVERNIGHT SHIFT
Agentic APIs & Orchestration Layers
The frameworks for products that need their own internal workforce.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
5
TOOLS
PYENV
WIRE
N/A
THIS BUILD
No agentic feature in this build. The ledger says so rather than pretending.
THE PROOF LEDGER →WHAT
What it is
Five entries: LangGraph, CrewAI, AutoGen AgentChat, Google GenAI and the agent-mesh placeholder that is not published upstream.
WHY
Why it exists
Some products need a graph, a crew, a critique loop or a two-million-token code read. Those are real architectures; they should be selected, not improvised.
HOW
How it runs
Python packages live in the shared pyenv; npm entries install into projects. Run ledgers keep tokens, retries and failure modes inside the budget.
WHEN
When it runs
Multi-agent features inside a product, automated critique loops, large-context analysis. Not for a brochure site.
WHO
Who owns it
CEO owns framework selection; Research watches the frontier; Build writes graphs and crews; Data tracks tokens and failures; Ops runs every path end to end.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
langgraph
pypiMulti-agent cyclic graphs — precise state models and custom retry conditions.
crewai
pypiRole-playing multi-agent crews (copy agent, UI agent, WebGL-optimizer agent).
autogen
pypiMicrosoft multi-agent conversation framework — agents critique each other's code.
@google/genai
npmHigh-speed multimodal endpoints processing huge context fields (up to 2M tokens) — full codebase analysis in one call.
@bireme/agent-mesh
npmLow-latency routing protocol for high-concurrency internal agent networks.
5 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show agentapilayer$ engctl awaken agentapilayer$ engctl install agentapilayer --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
No agentic feature in this build. The ledger says so rather than pretending.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
N/A here. This site has no agentic feature; the honest proof is the absence.
The engine is the how. The brief is the start.