AEOS
--:--:--

OpenAI

DisconnectedAvailable

AI Providers · OpenAI · v1.0.0 · manifest schema 1.0

The second AI provider, and the reason capability resolution is not a formality: it serves the same `completion.create` and `embedding.create` capabilities Claude does. A future AI Runtime asking the Hub for a completion gets whichever provider is installed, enabled and healthy — failover between them is a Hub concern, not a caller concern.

Last sync
—
Health
—
Rate ceiling
500/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

0/100

Not installed. Nothing is measuring it.

Authentication

Unconfigured
Method
API Key
Credential
—
Last verified
never
Principal
—
Expires
Does not expire
Scopes held
0/3
Scopes
  • completions:write
  • embeddings:write
  • models:read
Handshake · API Key
  1. 1.InitiateThe Hub prepares a API Key request for OpenAI.
  2. 2.Supply api keyEntered once. Held by reference — the Hub stores no credential material.
  3. 3.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.

Capabilities3

  • Create completionscompletion.create

    Run an inference as a fallback provider.

  • Create embeddingsembedding.create

    Vectorise memory records for the retrieval layer.

  • List modelsmodel.list

    Enumerate available models.

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

0
Calls
0
Records
0ms
Mean latency
0%
Error rate
500/min
Rate ceiling
declared by the manifest
0%
Peak usage
saturates at 80%
Peak consumption against ceiling

Event Subscriptions1

  • Memory Writtenmemory.written

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

    Raised by memory · see the fan-out chain

Publisher

First party
Name
AI-EOS
Publisher ID
aeos
Platform vendor
OpenAI
Support
operations@ai-eos.internal

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

OpenAI 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
9 months ago

Requires platform 1.0.0 or newer. This build is 1.0.0.

  • 1.0.0major · 9 months ago
    • First release. Declares the same completion and embedding capabilities as the primary provider, which is what makes capability resolution more than a formality.

Permissions and scopes

viewer+

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.

  • memory:read4 roles

    Memory records across every scope the caller may see.

Requested external scopes
  • completions:write
  • embeddings:write
  • models:read

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
API Key
Credential storage
Never stored
External scopes
3
AI-EOS permissions
1
Minimum role
viewer
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
2 capabilities
Data entering AI-EOS
1 capabilities
Modules served
2
Event topics received
1

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.

Documentation2

Logs1

  • Registry—Not installed. The Hub holds a manifest for this connector but no connection.

Roadmap

  • Automatic failover when the primary provider is degraded
  • Cost-aware routing between providers per task class

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