Integration Hub

The Integration Hub is the central layer that allows Orbit Agents to securely connect to external systems—whether that’s a SaaS API, a database, or an internal business service.
It standardizes authentication, routing, and compliance so every agent can safely use integrations without duplicating code or credentials.

Why the Integration Hub?

• Unified Access – Agents consume integrations via a consistent schema, reducing complexity.
• Security First – Credentials are vaulted, never exposed directly to agents.
• Scalability – Reuse integrations across multiple agents and business units.
• Governance – Enforce RBAC, rate limits, and compliance rules at the integration level.
• Observability – Monitor requests, errors, and performance across all connected systems.

How It Works

1. Register an Integration

   • Your team registers integrations in your environment (e.g., Salesforce, Stripe, S3).
   • Define required authentication (OAuth, API key, HMAC, etc.).
   • Configure scopes, rate limits, and compliance flags.

2. Agents Consume the Integration

   • Agents declare integration dependencies in their ai-tools.json.
   • The Hub automatically injects secure connection details at runtime.
   • All requests flow through the Hub’s audit and governance layer.

3. Execution & Monitoring

   • When invoked, agents call the Hub instead of direct external APIs.
   • The Hub logs request/response details, applies policies, and relays results.

Supported Integration Patterns

• Direct API Calls – REST or GraphQL requests with authentication handled by the Hub.
• Webhook/Event Subscriptions – Route external events into agents for real-time triggers.
• Data Connectors – Prebuilt adapters for databases (Postgres, MongoDB, DynamoDB, etc.).
• SaaS Connectors – Salesforce, Stripe, HubSpot, AWS, GCP, and more.
• Custom Connectors – Build your own integration schema for internal systems.

Example: Stripe Integration

{
  "name": "stripe-integration",
  "type": "integration",
  "auth": {
    "method": "api_key",
    "vault": "aws-kms"
  },
  "capabilities": {
    "tools": [
      {
        "name": "payments.create",
        "description": "Create a new Stripe payment",
        "inputSchema": {
          "type": "object",
          "properties": {
            "customerId": { "type": "string" },
            "amount": { "type": "number" },
            "currency": { "type": "string" }
          },
          "required": ["customerId", "amount"]
        }
      }
    ]
  }
}

In this example:

• Agent references stripe-integration in its metadata.
• Integration Hub injects secure API keys and routes the call to Stripe.
• Logs & compliance are automatically enforced.

Security & Compliance

• Secrets Management: Keys stored in KMS or HSM, never exposed to agents.
• Access Controls: Integration usage governed by RBAC at org/account/agent level.
• Audit Trails: Every request is logged for compliance.
• Rate Limiting: Prevent abuse and enforce vendor API limits.
• Compliance Flags: PCI, HIPAA, and Orbit Protocol alignment.

Best Practices

• Reuse integrations across agents rather than embedding credentials in each.
• Always scope integrations to the minimum required permissions.
• Validate input/output schemas when defining custom connectors.
• Monitor integration usage in the Console for optimization.

Tip: The Integration Hub is the recommended way to connect Orbit Agents to any external system. It ensures that integrations remain secure, reusable, and compliant across the entire Orbit ecosystem.