Source: docs/integration/agent-consumer-pack.md

Forgium Agent — integration package

This exported package is the public contract for an external developer or AI

agent integrating an application with Forgium Agent. It contains no platform

operator credentials or internal service configuration.

> Compatibility URL: the canonical agent entrypoint is

> Use Forgium Agent with an agent. This page remains

> available so existing public links do not break.

Start here

Read the documents in this order:

  1. Overview — what Forgium Agent does and which integration path to choose.
  2. Getting started — receive the access bundle and send the first HTTP message.
  3. Environments — isolate development, staging, and production.
  4. Choose the task-specific guide:

- Business capabilities for live data or actions from the host application.

- OpenAPI for the complete Public API contract.

Autonomous implementation agents must also read

skill/micro-agent-integrator/SKILL.md.

Authority boundary

The Forgium administrator provides this access bundle:

FORGIUM_AGENT_BASE_URL=https://<public-api-host>
FORGIUM_AGENT_API_KEY=mg_xxx

Use the API key with the Public API (/v1/*) to send messages and manage

business capabilities. If either value is missing, ask the administrator.

Do not request platform-operator credentials or access to internal services.

Completion paths

| Goal | Completion condition |
|---|---|
| Send a message from a host application | A request to `POST /v1/channels/http/messages` returns an assistant message. |
| Give the agent live business data or an action | A scoped host endpoint is imported, contract-tested, activated, and verified through chat. |

A generic response to a domain query usually means the required business

capability is absent or inactive. Follow the complete lifecycle in

capability-handoff.md; do not substitute chat

middleware, a proxy workaround, a placeholder URL, or an unauthenticated host

endpoint.