AEOS
--:--:--

Integration Registry

Every manifest the Hub knows about, with its version, capabilities, event subscriptions, permissions and authentication state. The tables below are a straight rendering of the configuration the Hub actually reads, so this page cannot fall out of step with its behaviour.

12
Registered
manifests
9
Installed
9 enabled
144
Capabilities
distinct
18
Event topics
routable

Manifest schema version 1.0. Every connector declares the schema it was written against, so an older manifest can be rendered as needing migration rather than crashing on a field that does not exist yet.

Installed Plugins12

ConnectorVersionSchemaInstallAuthCapsTopicsRuntimeHealth
GitHubv2.0.01.0InstalledAuthenticated21321/21100
Google Workspacev2.1.01.0InstalledAuthenticated28628/28100
Slackv1.0.01.0InstalledAuthenticated411—61
Discordv0.9.01.0AvailableUnconfigured23——
Shopifyv2.0.01.0InstalledAuthenticated37337/3788
Stripev2.0.01.0InstalledPending45245/4546
Claudev1.0.01.0InstalledAuthenticated323/384
OpenAIv1.0.01.0AvailableUnconfigured31——
Emailv1.0.01.0InstalledAuthenticated23—62
Calendarv0.8.01.0AvailableUnconfigured22——
Webhookv1.0.01.0InstalledNot required20—95
REST APIv1.0.01.0InstalledPending22—70

Provider Runtimes5

A manifest declares what a connector is; a provider supplies what it does. Most connectors have no runtime and are complete without one — they resolve, route and report health from the manifest alone. The rows below are the connectors whose capabilities can actually be invoked, read straight from PROVIDERS. Registering another is one array entry and no change to this page.

  • GitHubruntime v1.0.0 · contract 1.021/21 served

    Implements all twenty-one capabilities the GitHub manifest declares, validates the six configuration fields the development category defines, counts what the connection holds, and declares the topics, workflow actions, graph entities, insights, metrics and agent archetypes this connector offers the rest of the platform. Operations are described rather than performed — the request shape, the returned figures and the topics raised are the ones a real implementation has.

    Operationsrepo.readorg.readissue.readpr.readcommit.readbranch.readrelease.readpipeline.readpipeline.run.readdiscussion.readproject.readlabel.readmilestone.readcontributor.readcode.searchissue.writepr.writepr.reviewbranch.writerelease.writepipeline.trigger
    Raisesgithub.issue.createdgithub.issue.closedgithub.pull_request.createdgithub.pull_request.mergedgithub.pull_request.approvedgithub.branch.createdgithub.branch.deletedgithub.release.publishedgithub.workflow.completed
  • Google Workspaceruntime v1.0.0 · contract 1.028/28 served

    Implements all twenty-eight capabilities the Google Workspace manifest declares across Drive, Docs, Sheets, Slides, Gmail, Calendar, Meet, Contacts and the admin directory; validates the nine configuration fields the productivity category defines; counts what the connection holds; and declares the topics, workflow actions, graph entities, insights, metrics and agent archetypes this connector offers the rest of the platform. Operations are described rather than performed — the request shape, the returned figures and the topics raised are the ones a real implementation has.

    Operationsfile.readfile.searchfolder.readpermission.readrevision.readdoc.readsheet.readslide.readcomment.readmail.readcalendar.readdirectory.readcontact.readmeet.readfile.writefolder.writestorage.syncpermission.writedoc.writesheet.appendsheet.writeslide.writecomment.writemail.sendmail.draftcalendar.writemeet.writecontact.write
    Raisesgoogle.file.createdgoogle.file.updatedgoogle.folder.synchronisedgoogle.sync.completedgoogle.permission.grantedgoogle.permission.revokedgoogle.document.publishedgoogle.sheet.appendedgoogle.comment.addedgoogle.mail.sentgoogle.calendar.event.createdgoogle.calendar.event.updatedgoogle.calendar.event.cancelledgoogle.meet.scheduledgoogle.meet.startedgoogle.contact.added
  • Shopifyruntime v1.0.0 · contract 1.037/37 served

    Implements all thirty-seven capabilities the Shopify manifest declares across products, collections, orders, customers, inventory, locations, discounts, draft orders, gift cards, fulfilment, shipping, markets, metafields, files, online-store content, themes, apps and analytics; validates the seven configuration fields the commerce category defines; enforces the operator's resource narrowing per operation; counts what the store holds; and declares the topics, workflow actions, graph entities, insights, metrics and agent archetypes this connector offers the rest of the platform. Operations are described rather than performed — the request shape, the returned figures and the topics raised are the ones a real implementation has.

    Operationsproduct.readcollection.readorder.readcustomer.readinventory.readlocation.readdiscount.readgiftcard.readdraftorder.readfulfilment.readshipping.readmarket.readmetafield.readasset.readpage.readblog.readtheme.readapp.readanalytics.readcatalogue.writeproduct.writeproduct.archivecollection.writeorder.writeorder.cancelfulfilment.writedraftorder.writecustomer.writecustomer.taginventory.syncinventory.adjustdiscount.writegiftcard.writemetafield.writeasset.writepage.writeblog.write
    Raisesshopify.product.updatedshopify.product.createdshopify.order.cancelledshopify.inventory.changedshopify.order.fulfilledshopify.customer.createdshopify.sync.completedshopify.discount.created
  • Striperuntime v1.0.0 · contract 1.045/45 served

    Serves forty-five payment, subscription, invoice and treasury capabilities. Validates the account, the environment and the key mode; enforces the operator's resource narrowing per operation; counts what the account holds; and declares twenty topics onto the existing bus.

    Operationspayer.readpaymentmethod.readpayment.readrefund.readcheckout.readinvoice.readsubscription.readsubscriptionitem.readbillingproduct.readprice.readdispute.readpayout.readbalance.readbalancetransaction.readconnectedaccount.readusagerecord.readtax.readpayment.createpayment.cancelrefund.writepaymentlink.writecheckout.writeinvoice.paypayout.writedispute.writepayer.writepayer.archivepaymentmethod.attachpaymentmethod.detachinvoice.writeinvoice.finaliseinvoice.sendinvoice.voidsubscription.writesubscription.cancelsubscription.pausesubscriptionitem.writebillingproduct.writebillingproduct.archiveprice.writecoupon.writepromotioncode.writeconnectedaccount.writeusagerecord.writetaxrate.write
    Raisesstripe.payment.createdstripe.payment.succeededstripe.payment.failedstripe.payment.refundedstripe.balance.updatedstripe.invoice.paidstripe.invoice.failedstripe.payout.createdstripe.payout.failedstripe.dispute.updatedstripe.customer.createdstripe.customer.updatedstripe.invoice.createdstripe.subscription.createdstripe.subscription.updatedstripe.subscription.cancelled
  • Clauderuntime v1.0.0 · contract 1.03/3 served

    Implements the three capabilities the Claude manifest declares. Operations are described rather than performed — the request shape, the returned figures and the topics raised are the ones a real implementation has, so becoming real is a change of body rather than of contract.

    Operationscompletion.createembedding.createmodel.list
    Raisesruntime.completionruntime.embedding

Provider contract version 1.0, versioned separately from the manifest schema above: a plugin and a manifest can change independently, and pretending otherwise would force one to be revised for the other's reasons.

Capabilities144

Derived from the manifests rather than authored, which is what keeps the vocabulary self-maintaining. A capability with two providers gives its consuming modules a fallback.

Supported Events18

  • workflow.completedWorkflow Completedraised by workflows

    A workflow reached its final stage with every gate cleared.

  • workflow.blockedWorkflow Blockedraised by workflows

    A workflow stalled on a dependency or an unapproved gate.

  • approval.requestedApproval Requestedraised by workflows

    A gate opened and is waiting on an executive seat.

  • company.createdCompany Createdraised by companies

    A new autonomous company workspace was generated.

  • decision.criticalCritical Recommendationraised by decision-engine

    The advisory layer raised something at critical priority.

  • alert.raisedAlert Raisedraised by decision-engine

    A threshold was crossed anywhere in the estate.

  • agent.deployedAgent Deployedraised by agents

    An AI employee was installed into a department.

  • memory.writtenMemory Writtenraised by memory

    A record entered the retention layer and may need filing externally.

  • message.broadcastBroadcast Sentraised by communications

    An executive announcement went out to the estate.

  • report.generatedReport Generatedraised by intelligence

    The analytics layer produced a consolidated read.

  • runtime.completionModel Completionraised by integrations

    An inference finished. Raised by the Hub until the AI Runtime owns it.

  • runtime.embeddingVectors Writtenraised by integrations

    Records were vectorised for retrieval. Raised by an AI provider runtime until the AI Runtime owns it.

  • plugin.installedPlugin Installedraised by integrations

    An operator added a plugin to this tenant's estate and its pre-flight passed.

  • plugin.enabledPlugin Enabledraised by integrations

    A disabled plugin resumed routing. Its configuration and credentials were retained.

  • plugin.disabledPlugin Disabledraised by integrations

    A plugin stopped routing without being uninstalled.

  • plugin.updatedPlugin Updatedraised by integrations

    An operator took a published version. Also raised by a rollback — the recorded version changed either way.

  • plugin.removedPlugin Removedraised by integrations

    A plugin left the estate and its configuration was discarded. The manifest stays in the registry.

  • plugin.failedPlugin Failedraised by integrations

    A lifecycle operation was refused — incompatible platform, missing dependency, conflict, or an ungrantable permission.

Authentication Methods6

  • OAuth 2.0expires in 720h

    Operator authorises on the provider's site; the Hub stores a refresh reference.

    Requires: Client ID, Client secret, Redirect URI, Scope grant

  • API Keyno expiry

    A long-lived key pasted once. No redirect, no refresh, no expiry.

    Requires: API key

  • Personal Access Tokenexpires in 8760h

    A long-lived token minted by a named human and scoped by them. Acts as that person, not as the platform.

    Requires: Personal access token, Token scopes, Owning account

  • Bearer Tokenexpires in 24h

    A short-lived token presented per request. Refreshed by the Auth Manager.

    Requires: Token endpoint, Client credentials

  • Service Accountexpires in 2160h

    A machine identity with a signed key. Acts as itself, not as the operator.

    Requires: Account email, Private key reference, Domain delegation

  • No Authenticationno expiry

    An open or inbound-only transport. Nothing to authenticate.

The methods differ in exactly two observable ways — what the operator supplies, and whether the credential lapses. Both are fields above, which is why a sixth method is a row here and no change to the Auth Manager.

Categories16

  • Developmentfan-out 20

    Source control, CI and issue tracking.

  • Commercefan-out 10

    Storefronts, payments and billing. Fans out first — money moves before anyone is told.

  • Messagingfan-out 30

    Anywhere a human or a channel is notified.

  • Productivityfan-out 40

    Documents, drives, calendars — where output is filed.

  • AI Providersfan-out 50

    Model inference. The seam the future AI Runtime plugs into.

  • Analyticsfan-out 60

    Where events are recorded for later reading. Fans out last, by design.

  • Protocolfan-out 70

    Generic transports — not a vendor. The escape hatch for anything unlisted.

  • Securityfan-out 5

    Identity, secrets, scanning and audit. Fans out FIRST — a system that records what happened must hear before anything acts on it.

  • Financefan-out 15

    Accounting, payroll and treasury. Shares commerce's accent because it is the same money, one ledger later.

  • CRMfan-out 25

    Customer records and pipelines. The customer is updated after the transaction, not before it.

  • Marketingfan-out 35

    Campaigns, audiences and attribution. After humans are notified, because an audience is not an alert.

  • Databasefan-out 45

    Managed stores, warehouses and vector indexes. Durable writes land before anything reads them.

  • Automationfan-out 55

    Schedulers and no-code runners that act on an event. Late, because they trigger further work.

  • Cloudfan-out 65

    Object storage, queues, compute and secret managers.

  • Operationsfan-out 68

    Incident, ticketing and on-call. Near the tail — an operations record follows the operation.

  • Otherfan-out 80

    Declared but unclassified. Fans out last so an unclassified connector never preempts a classified one.

Thresholds13

Every number the Hub tests against, in one place. Retuning is configuration, not code — a future settings UI writes to this table and nothing else changes.

ThresholdValueUnitMeaning
Credential renewal window72hours remainingInside this window a credential reads as expiring rather than valid.
Degraded error rate2% of callsAbove this share of failing calls the connector is degraded, not healthy.
Critical error rate8% of callsAbove this the connector is failing and the gateway should shed its traffic.
Slow gateway response800ms meanMean round trip above this is slow enough for a caller to notice.
Rate ceiling saturation80% of limitPeak consumption above this share of the documented ceiling risks throttling.
Webhook failure rate5% of deliveriesAbove this share of failed inbound deliveries the endpoint is failing.
Webhook replay window300secondsA signed delivery whose timestamp is further from now than this — in either direction — is refused as a replay.
Webhook retry rate10% of eventsAbove this share of inbound events needing a retry, the inbound path is struggling rather than merely busy.
Webhook dead letters3entriesDead-lettered events above which inbound needs an operator. Every entry here is an event AI-EOS accepted and never acted on.
Webhook processing time500ms meanMean time from receipt to queue admission above which acknowledgement is slow enough for a platform to time out and redeliver.
Sync backlog6queued jobsQueued jobs above which the synchroniser is not keeping up with intake.
Error backlog4entriesUnresolved errors above which the estate needs operator attention.
Connector health floor70/100Matches HEALTH_WARN in lib/utils. Below it a connector reads degraded.