Integration · Internal HTTP endpoint
Connect internal HTTP endpoints through Outpost
Make an internal HTTP API available to selected assistants through a controlled connection.
An internal HTTP endpoint can be made available to selected assistants through the meinGPT Outpost. The API does not need to be exposed publicly; the Outpost carries only services registered on the device and shared in meinGPT.
An administrator configures the base URL, authentication and access on the Outpost. The service then appears in meinGPT and must be shared deliberately. An assistant can subsequently run the intended API calls through the existing Outpost connection.
- Source
- Internal HTTP endpoint
- Capability
- Run approved internal API calls from assistants
- Connection
- Administrator registration on the Outpost, sharing in meinGPT and credentials stored on the device
- Data residency
- The endpoint and connection secrets remain on the local network; calls travel through the outbound Outpost connection
Source, permissions, and data residency are documented separately for each connector.
Typical workflows
- Retrieve internal data
- Trigger business processes
- Connect legacy systems
What the integration makes possible
01
Retrieve internal data
Use defined information from an API on the local network in an answer.
02
Trigger business processes
Invoke explicitly approved HTTP actions from an assistant.
03
Connect legacy systems
Use an existing internal API without publishing a public connector.
Review the prompt and result openly
Retrieve the shipping status for order 8402 from the internal API.
Result
Order 8402 has been picked and is scheduled to ship on 21 August.
Does this connection fit your use case?
We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.
Security and operations
Only administrators register and share the service. Credentials remain on the Outpost; the target API should enforce authentication, minimal permissions and its own checks for write operations.
Known limitations
- 01Private Beta. Methods, validation and write effects must be configured and reviewed for the specific API.
Frequently asked questions
No. The Outpost establishes the outbound connection and carries the approved calls.