AEOS
--:--:--

REST API

Pending authInstalled

Protocol · Generic (outbound) · v1.0.0 · manifest schema 1.0

The generic outbound transport, and the other half of the escape hatch. Configure a base URL and any unlisted SaaS platform, internal company system or future API is callable through the same gateway, with the same rate accounting, health monitoring and error queue every named connector gets. Permanent, for the same reason the inbound door is.

Last sync
2h ago
Health
70/100
Rate ceiling
600/min
Webhooks
not supported

Add to the estate and begin the authentication handshake. Every operation is a state transition inside AI-EOS — no external service is contacted.

Health

70/100

70/100 — Handshake incomplete — the connector is installed but not yet authorised.

  • −30CredentialHandshake incomplete — the connector is installed but not yet authorised.

Authentication

Pending
Method
Bearer Token
Credential
—
Last verified
never
Principal
—
Expires
Does not expire
Scopes held
0/1
Scopes
  • configured-per-endpoint
Handshake · Bearer Token
  1. 1.InitiateThe Hub prepares a Bearer Token request for Generic (outbound).
  2. 2.Supply token endpointEntered once. Held by reference — the Hub stores no credential material.
  3. 3.Supply client credentialsEntered once. Held by reference — the Hub stores no credential material.
  4. 4.VerifyThe Hub performs one authenticated read to confirm the grant, then records the reference.

Nothing is contacted. The Hub stores no credential material — only a masked reference, the granted scopes and an expiry. There is no field on the auth record a secret could go in, which is a stronger guarantee than a policy of not putting one there.

Capabilities2

  • Issue requestshttp.request

    Call any configured endpoint through the gateway.

  • Poll endpointshttp.poll

    Fetch on a schedule and raise changes on the bus.

Modules request capabilities, never connectors. A capability offered by two connectors gives the requesting module a fallback it does not have to know about.

Usage · 24h

51,840
Calls
362,880
Records
325ms
Mean latency
0.6%
Error rate
600/min
Rate ceiling
declared by the manifest
24%
Peak usage
saturates at 80%
Peak consumption against ceiling

Event Subscriptions2

  • Workflow Completedworkflow.completed

    A workflow reached its final stage with every gate cleared.

    Raised by workflows · see the fan-out chain

  • Alert Raisedalert.raised

    A threshold was crossed anywhere in the estate.

    Raised by decision-engine · see the fan-out chain

Publisher

First party
Name
AI-EOS
Publisher ID
aeos
Platform vendor
Generic (outbound)
Support
operations@ai-eos.internal

Published by the platform itself. These manifests ship with the build rather than being fetched.

Generic (outbound) owns the platform this plugin reaches. AI-EOS authored the manifest.

Version and changelog

Up to date
Installed
1.0.0
Published
1.0.0
Minimum platform
1.0.0
Compatibility
Compatible
Manifest schema
1.0
First published
16 months ago

Requires platform 1.0.0 or newer. This build is 1.0.0.

  • 1.0.0major · 7 months ago
    • The outbound door. Any HTTP system is reachable through it without a manifest of its own.
    • Permanent: removing it would strand every unlisted system configured to use it.

Permissions and scopes

operator+

AI-EOS permissions are what this plugin may do insidethe platform, resolved against the API Gateway’s own table. Scopes are what the external platform is asked to allow. They are different systems and neither substitutes for the other.

  • integration:write3 roles

    Route a capability call through the Integration Hub to a connector.

  • workflow:read4 roles

    Workflows, stages, tasks and approval gates.

  • analytics:read4 roles

    Enterprise Intelligence read models and the Decision Engine's outputs.

Requested external scopes
  • configured-per-endpoint

Dependencies0

Declares no dependencies. It can be installed against an empty estate.

Whether each is satisfied is resolved against the live estate at install time, not here.

Security

Authentication
Bearer Token
Credential storage
Never stored
External scopes
1
AI-EOS permissions
3
Minimum role
operator
Inbound deliveries
Not accepted
Tenant isolation
Installation state is tenant-scoped

A plugin is a data literal. Nothing in the marketplace executes plugin code, and a plugin cannot bypass the Authentication Manager, the Integration Hub, the API Gateway or a permission check, because it has no code path — the host performs every transition.

The auth state type has no field a credential fits in, so the guarantee is enforced by the type checker rather than by convention.

Privacy

Data leaving AI-EOS
1 capabilities
Data entering AI-EOS
1 capabilities
Modules served
4
Event topics received
2

Direction is declared per capability, so what this plugin can send and what it can receive are both enumerable rather than a matter of trust. It reaches only the modules listed above, and only through capabilities the Integration Hub resolves.

Documentation1

Logs4

  • Authjust nowInstalled, but configuration is required before the handshake can complete.
  • Sync1h agoSynchronisation completed — 362,880 records reconciled in 24h.
  • Gateway35m ago51,840 gateway calls in 24h at 325ms mean latency.
  • Registry5d agoConnector v1.0.0 installed against manifest schema 1.0.

Roadmap

  • Operator-defined capability declarations per configured endpoint
  • An OpenAPI import that generates a named manifest automatically

What this connector would gain next. Mirrors the Future Integrations list every module carries in the Navigator registry.