Enterprise API handoff
Independent AI decision accountability for high-consequence decisions. This is a server-to-server API; never place Forge credentials in browser code.
Start here
- One-page enterprise integration path
- Integration quickstart
- Starter OpenAPI: five reviewable operations, including durable key self-readback
- Enterprise agent accountability OpenAPI: ten post-onboarding tenant-control and runtime operations, including durable key-authority readback
- Complete product OpenAPI
- Machine-readable integration status
- Executable synthetic presets
- Signing identity readback (comparison only; not trust bootstrap)
- Signed integration artifact manifest
Run the reviewed bootstrap before downloading the kit
Authenticated onboarding separately delivers four bootstrap files: forge_bootstrap_first_call.py, both standalone artifact verifiers, and requirements-verifier.lock. It also delivers the reviewed SHA-256 of each file, the production artifact public key and full key ID, and the approved source commit. Compare the local bootstrap bytes with the separately delivered hash before invoking the script; a script cannot establish its own pre-execution integrity. Same-origin copies and the API identity endpoint are readback only and cannot establish trust.
python3.11 -c 'import hashlib, os, pathlib, sys; actual = hashlib.sha256(pathlib.Path("forge_bootstrap_first_call.py").read_bytes()).hexdigest(); expected = os.environ["FORGE_BOOTSTRAP_SHA256"].lower(); sys.exit(0 if actual == expected else "bootstrap SHA-256 mismatch")'
python3.11 forge_bootstrap_first_call.py \
--api-origin "$FORGE_BASE_URL" \
--artifact-key-id "$FORGE_INTEGRATION_ARTIFACT_SIGNING_KEY_ID" \
--artifact-public-key-b64 "$FORGE_INTEGRATION_ARTIFACT_PUBLIC_KEY_B64" \
--source-commit "$FORGE_RELEASE_COMMIT_SHA" \
--expect-bootstrap-sha256 "$FORGE_BOOTSTRAP_SHA256" \
--expect-root-verifier-sha256 "$FORGE_ROOT_VERIFIER_SHA256" \
--expect-bundle-verifier-sha256 "$FORGE_BUNDLE_VERIFIER_SHA256" \
--expect-verifier-lock-sha256 "$FORGE_VERIFIER_LOCK_SHA256" \
--destination forge-first-call-kit
The bootstrap repeats the local-file hash check before networking as defense in depth, refuses redirects, authenticates the signed root, downloads only the signed content-addressed archive, verifies every declared member, and extracts into a new directory without links, traversal, or overwrite. The commands below are the auditor-readable expansion of that protocol; a team that ran the bootstrap must not download or extract a second copy.
python3.11 -m venv .forge-verifier .forge-verifier/bin/python -m pip install --require-hashes --only-binary=:all: \ -r requirements-verifier.lock .forge-verifier/bin/python forge_verify_artifact_manifest.py forge-integration-manifest.json \ --expect-key-id "$FORGE_INTEGRATION_ARTIFACT_SIGNING_KEY_ID" \ --expect-public-key-b64 "$FORGE_INTEGRATION_ARTIFACT_PUBLIC_KEY_B64" \ --expect-source-commit "$FORGE_RELEASE_COMMIT_SHA" .forge-verifier/bin/python forge_verify_artifact_bundle.py forge-first-call-kit.zip \ --expect-key-id "$FORGE_INTEGRATION_ARTIFACT_SIGNING_KEY_ID" \ --expect-source-commit "$FORGE_RELEASE_COMMIT_SHA" \ --expect-archive-sha256 "$FORGE_FIRST_CALL_ARCHIVE_SHA256"
Runnable examples
Run the examples from the verified forge-first-call-kit directory created by the bootstrap. It contains the canonical Python and curl examples, offline verifier, golden proof, and only the Python runtime modules those examples need. The full diligence and implementation kit is a different signed archive and must be verified against its own separately delivered manifest and archive SHA-256 values before use.
- Python descriptor-first call (recommended)
- curl transport diagnostic (manual pins)
- JavaScript transport diagnostic (manual pins)
- TypeScript descriptor-first call
- TypeScript protected-boundary implementation
SDK source bundles
Enterprise operations
The downloadable examples use synthetic data. Execution remains in the customer-controlled boundary; Forge evaluates, records, signs, and returns a disposition.