syntropAI
One server per SDK, not one tool per service.
1 coreevery SDK plugs into, reaching all its services
~175 linesis the whole core, each SDK adds about a page
Any SDKAWS, Oracle, Azure, Google Cloud, market data and compliance
The problem
When AI agents learned to use tools, most servers wrapped cloud APIs one tool per service. One provider has hundreds of services, every provider needs its own set, and a new service waits until someone writes its tool.
syntropAI gives the agent the whole SDK instead. The agent writes the code, and every line is checked before it runs.
The insight
Clouds, markets and project tools look nothing alike. Underneath, they share one shape.
| Cloud | Finance | Projects | |
|---|---|---|---|
| Resource | VM, storage | Stock, bond | Issue, story |
| Collection | Resource group | Portfolio | Workflow |
| Operation | Provision, scale | Buy, sell | Create, update |
| Constraint | Cost, region, compliance | Risk, exposure | Budget, timeline |
How it works
1AskSay what you want in plain language.
2WriteThe agent writes code against the provider’s own SDK.
3CheckThe code is read as a syntax tree first. Only allowed modules, no dangerous calls, an answer required.
4RunOnly then does it run, and the result comes back.
Under the hood
boto3OCIAzureGooglefinvizOSCAL
Each SDK plugs in with its login and a namespace, about a page of code.
→
syntropaibox
Being addedDescribeReads the SDK’s own catalogue: services, methods and exact parameters.
RunParse into a syntax tree, check imports and calls, run with the session, return JSON.
→
AI agentThrough MCP. It looks up the SDK, writes the code, and gets the result.
Many SDKs, one core, the same two abilities for each.
What was built
- syntropaibox. The shared core: a login contract every provider fills in, and a guarded runner that checks code before running it.
- AWS, Oracle Cloud, Azure and Google Cloud. About a page of code each. Every service of that cloud through one tool.
- Guarded execution. Only the SDK and a short list of safe libraries may be imported. eval and exec are blocked, built-ins are reduced, and the code must return an answer. Errors go back to the agent, so it can correct itself.
- Beyond cloud. The same core on finviz for market data, and on NIST OSCAL for security compliance.
- Reading the SDK first. Every SDK already describes itself: AWS through its service models, Google Cloud through its discovery documents, OSCAL through its schemas. A read-only tool is being added to hand that catalogue to the agent before it writes code.
- One sentence, all clouds. On top of it, demos of governed provisioning, live cost and compliance reports across clouds.
Built with