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

Copy this prompt into your agent. It makes the public documentation the canonical contract and, when supported, uses the Forgium Agent Integrator Skill as the guided workflow.

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

Read these pages in order before changing code:
1. https://docs.forgium.dev/docs/integration/overview.html
2. https://docs.forgium.dev/docs/integration/getting-started.html
3. https://docs.forgium.dev/docs/integration/environments.html
4. Choose the relevant HTTP, capabilities, and API reference pages.
5. When the runtime supports Agent Skills, read the Forgium Agent Integrator Skill at
   https://docs.forgium.dev/docs/skill/micro-agent-integrator/SKILL.html. Treat it
   as the execution workflow; the public documentation remains the canonical contract.

Before changing code, confirm that these values are available for the target
environment:
- FORGIUM_AGENT_BASE_URL
- FORGIUM_AGENT_API_KEY

If either value is missing, ask the Forgium administrator to provide it. Use
only the public API and documentation. Do not request platform-operator
credentials or access to internal services.

First perform the authenticated HTTP smoke test. Inspect this repository and
choose the integration path it actually needs:
- HTTP for a synchronous host-application response; or
- capabilities when the agent needs approved live business data or actions.

If capabilities are needed, follow the complete public capability lifecycle:
create a scoped HTTPS host endpoint, provision its credential through the
Public API vault, create a secret-free manifest, import it, contract-test it,
activate it, and verify the result through chat. Repeat this separately for
each environment. Never use a placeholder URL or an unauthenticated endpoint.

Implement the integration in this repository, run its tests, and verify an
end-to-end request. Report exactly one concrete blocker if an authorized
endpoint deployment or HTTPS exposure step is unavailable. Do not claim that a
capability is active unless activation and the final chat verification pass.

Read the complete agent-integration guide

Get started

Integrate

integration/capability-handoff.md

Reference

Skill