Skip to main content
Most products only need the default embed and per-session tools. Use these when sandbox work needs credentials your product owns, or when your product must react to agent events.
Configure the credential provider and webhooks per workspace or once for the organization; see Webhooks and credentials. Each signing secret is returned once, at creation.

One signature scheme

Every request Opengeni sends to your endpoints is signed:
Verify the raw body before parsing it:

Credential provider

An HTTPS endpoint that supplies short-lived credentials for sandbox work: environment variables, files, Git credentials, and MCP credentials. Opengeni calls it before a turn’s sandbox work and again before they expire.
Each request names the workspace, session, turn, and the user who started the work, so you can scope credentials to them. Respond with ok plus the credentials and an optional expiresAt, not_applicable, or auth_needed with a message to show the user. For multiple Git installations on one host, return a renewable repository-scoped helper through files and fileEnvironment, and configure it with environment.GIT_CONFIG_*. Set credential.useHttpPath=true and clear credential.helper before adding your helper. Opengeni preserves this declared helper chain during the initial clone as well as later Git commands; it does not inherit ambient image helpers. Explicit Opengeni connection selections remain separate.

Webhooks

Up to ten endpoints per workspace, each subscribed to any of:
The body identifies the session, turn, and sequence; read details through the API. Delivery is at least once and unordered: deduplicate on the event id and order by sequence. Failed deliveries retry with backoff; inspect and replay them with listWorkspaceWebhookDeliveries and redeliverWorkspaceWebhookDelivery.

Turn identity on MCP calls

Every MCP tool call includes _meta.opengeni with the workspace, session, turn, and initiating user. Use it for logging; authorize with the connection’s own credential.

Reference

Request and response bodies and retry schedules are in the workspace integrations reference.
Using a coding agent? The opengeni-client skill covers this.