API Proxy Setup

How the REST Proxy Works

In addition to MCP proxying, ShieldAgent can intercept REST API calls made by agents to external services (Stripe, Slack, internal microservices, etc.). Every request is authenticated, policy-checked, and audit-logged before forwarding.

Register an API Endpoint

Tell ShieldAgent which external endpoints your agents are allowed to reach:

SDK examples have been retired. For a supported integration, use the OpenAPI reference.

Configure Agent to Use the Proxy

Agents make REST calls to ShieldAgent instead of the external API directly. ShieldAgent forwards authenticated requests after policy evaluation.

# Instead of calling Stripe directly:
# curl https://api.stripe.com/v1/charges -H 'Authorization: Bearer sk_live_...'

# The agent calls the ShieldAgent proxy:
curl https://proxy.shieldagent.io/rest/stripe-charges \
  -H 'Authorization: Bearer <agent-key>' \
  -H 'Content-Type: application/json' \
  -d '{"amount": 2000, "currency": "usd", "source": "tok_..."}'

Per-Endpoint Policies

Apply method-level restrictions on top of endpoint registration:

{
  "tenantId": "<tenant-id>",
  "agentId": "<agent-id>",
  "toolName": "rest:stripe-charges",
  "action": "deny",
  "conditions": [
    {
      "type": "param_contains",
      "param": "method",
      "value": "DELETE"
    }
  ]
}

Response Filtering & DLP

ShieldAgent scans responses for sensitive data patterns (PII, secrets, card numbers) before returning them to the agent. Configure DLP rules per tenant:

SDK examples have been retired. For a supported integration, use the OpenAPI reference.