Start with an embedded SDK
For most applications, use the Node or Python SDK in the process that already calls the vendor API. Keep the vendor credentials that application already requires in its existing client or configuration. The embedded AGINDOW SDK needs no separate AGINDOW API key, dashboard session or HTTP endpoint. The quickstart selects a detector explicitly; without that setup, the default engine passes calls through without detecting drift.
Choose the boundary you own
These interfaces solve different integration needs. They are alternatives for specific jobs, not a sequence of services you must configure.
| Your goal | Use | What it does |
|---|---|---|
| Wrap a callable or existing API client | Embedded Node or Python SDK | Inspects calls inside your application. Keeps existing credentials and sync/async behavior. |
| Call an explicitly configured execution service | Guard HTTP API on your own host | POST /v1/guard executes one bound vendor tool. Use only if you intentionally run an HTTP guard. |
| Authenticate an admitted workload to that execution host | Optional workload identity exchange | POST /v1/token exchanges an existing identity for a scoped token. It does not execute tools or create an account. |
| Let an agent inspect contracts, findings or audit evidence | Read-only MCP interface | Reads evidence and simulates proposals; never executes a vendor write. |
| Try a labelled fixture without installing | Browser playground | Runs local fixture detection and source inventory; it does not call a vendor or affect production traffic. |
Recommended reading path
Run the quickstart, read the SDK reference for your language, then learn modes and outcome handling. Use the observe guide before considering stricter policy. Open HTTP or MCP references only when you choose those transports.
Use your coding agent
Give your agent the AGINDOW best-practices skill and name the callable or client you want to wrap. The skill follows the same SDK-first reading path and requires explicit detection setup.
Availability and safety
Embedded SDKs are published pre-alpha packages. AGINDOW does not currently operate hosted guard or MCP endpoints. The default engine detects nothing and has no selective repair output. Do not rely on a finding, successful installation or simulation as evidence that production writes are protected.