Source: docs/public-manifest.json

Forgium Agent — public documentation

Integration contract for external developers and AI agents. Does not include internal platform operations.

Integrate with your coding agent

Use the single agent integration entrypoint. The optional Skill source is not installable and is not part of the recommended navigation.

You are integrating my application with Forgium Agent. Use only the official
public integration documentation at https://docs.forgium.dev/docs.

Start with these canonical resources; do not guess or enumerate undocumented
URLs:
1. https://docs.forgium.dev/agent-manifest.json
2. https://docs.forgium.dev/docs/integration/use-with-an-agent
3. https://docs.forgium.dev/docs/integration/overview
4. https://docs.forgium.dev/docs/integration/environments
5. https://docs.forgium.dev/docs/integration/api.openapi.yaml

Use the manifest's published links for the selected route:
- HTTP quickstart: https://docs.forgium.dev/docs/integration/getting-started
- Capabilities lifecycle: https://docs.forgium.dev/docs/integration/capability-handoff
- Request access: https://docs.forgium.dev/docs/integration/request-access
- Contract retrieval: https://docs.forgium.dev/docs/integration/contract-retrieval
- HTTP integration reference: https://docs.forgium.dev/docs/integration/reference-implementation

If you are only testing connectivity, do not inspect or modify an unrelated
repository: use the access bundle and the HTTP quickstart to send one message.
Do not run repository or git discovery commands for a connectivity-only test.

If you are implementing code, first confirm the working directory with `pwd`
and explicitly inspect the host application's repository. Choose the minimum
integration it actually needs:
- HTTP when it needs a synchronous agent response; or
- capabilities when the agent needs approved live data or actions from the host.
Capabilities are optional and may coexist with HTTP.

When a real API call or deployment is required, confirm these values for the
selected environment before using them:
- FORGIUM_AGENT_BASE_URL
- FORGIUM_AGENT_API_KEY
If either is missing, ask the Forgium administrator for the environment-specific
access bundle and continue only with local implementation or mocks.

Read the canonical OpenAPI contract before generating requests. If the agent
cannot locate it through the published links, follow the Contract retrieval
commands once and report the exact result. Do not substitute another contract.
Implement only the applicable route, run tests, and record evidence. For capabilities, use the
public lifecycle: protect and expose the host endpoint, provision its scoped
credential through the Public API vault, create a secret-free manifest, import,
contract-test, activate, and verify through chat. Repeat separately per
environment. Never use a placeholder URL or an unauthenticated endpoint.

If a published page or the canonical contract is unavailable, stop and report
that blocker. Do not probe guessed OpenAPI, Swagger, API, or internal URLs.
Report every blocker separately with its next action.

Report changes, verification evidence, and every actionable blocker. Do not
claim a capability is active unless activation and final chat verification
pass. Never request Admin API access or internal secrets.

Machine-readable index

agent-manifest.json, agent-index.json, llms.txt, and llms-full.txt are generated from the public manifest. Agents must use the published links and must not guess undocumented URLs.

Recommended reading

  1. Agent decision protocol
  2. Integration overview
  3. Environments
  4. Manual HTTP quickstart
  5. Raw OpenAPI contract

Agent integration

Manual integration

Capabilities

Reference