Webhook

95/100 — 850ms mean round trip, above the 800ms threshold.

• −5Latency850ms mean round trip, above the 800ms threshold.

Method

○No Authentication

Credential

—

Last verified

—

Principal

—

Expires

Does not expire

Scopes held

0/0

• ←Receive deliverieswebhook.receive

  Accept a signed POST and raise it on the internal bus.

• ←Verify signatureswebhook.verify

  Check delivery signatures before routing.

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

This connector subscribes to no internal topics. It is called directly through the gateway rather than driven by events.

Name

AI-EOS

Publisher ID

aeos

Platform vendor

Generic (inbound)

Support

operations@ai-eos.internal

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

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

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 · 2 months ago
  • Signature verification over raw bytes across five schemes.
  • Scoped delivery paths, so two tenants sharing one path cannot cross-deliver.
  • Permanent: the inbound door cannot be uninstalled.

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:read4 roles

  The connector estate, its health and its event routing.

• integration:write3 roles

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

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.

Authentication

No Authentication

Credential storage

Never stored

External scopes

0

AI-EOS permissions

2

Minimum role

operator

Inbound deliveries

2 endpoints unverified

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.

Data leaving AI-EOS

0 capabilities

Data entering AI-EOS

2 capabilities

Modules served

3

Event topics received

0

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.

• Setup guide →

2 endpoints are accepting deliveries without signature verification. The generic inbound door ships this way because its signing secret is per-sender — configure one per registered sender before treating the path as trusted.

• ⟐/api/integrations/webhook/eventsactiveUnverified6,878 in · 3% failed · 4h ago

  Forwards operator-mapped

• ⟐/api/integrations/webhook/events/1activeUnverified4,302 in · 0% failed · 2h ago

  Forwards operator-mapped

• infoSync3h agoSynchronisation completed — 1,555,200 records reconciled in 24h.
• infoGatewayjust now172,800 gateway calls in 24h at 850ms mean latency.
• infoRegistry19h agoConnector v1.0.0 installed against manifest schema 1.0.

Roadmap

• ◇Per-endpoint replay of failed deliveries from the error queue
• ◇Operator-defined mapping from payload shape to internal topic

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