SDK options - Forge

Both SDKs need a server-side API key from the service’s Activity page. They use Forge’s current collector at https://app-api.forgeintel.co/api/sdk/v2 by default. Advanced deployments may override either URL; never derive a public URL from an incoming Host header.

Node `createForge()`	Python `Forge()`	Default	Purpose
`apiKey`	`api_key`	Required	Forge SDK key.
`backendUrl`	`backend_url`	`https://app-api.forgeintel.co/api/sdk/v2`	Optional collector override for a different Forge environment.
`publicUrl`	`public_url`	Same-origin paths	Optional public origin when absolute links are required.
`agentContext`	`agent_context`	off	`true` asks for agent type and search query on paid requests and records them, optional. `{ required: true }` (`AgentContextOptions(required=True)`) requires them: HTTP 400 before payment when missing. Agent context.
`openapi`	`openapi`	Intercept `/openapi.json`	Enrich a supported document; use a document provider or custom paths when needed.
`x402Discovery`	`x402_discovery`	`false`	Serve `/.well-known/x402`, the list of your paid resources that x402 indexes crawl, when your app doesn’t serve one. Resources come from your OpenAPI paid operations and the 402s Forge has seen; instructions from your `x-guidance`. A file you serve yourself is always kept.
`strict`	`strict`	`false`	Raise on invalid configuration instead of disabling instrumentation.

Node also offers describeChallenges, challengeExtension, receiptExtension, injectBody, injectText, rateHint, and flushIntervalMs. Python uses their snake_case equivalents where supported. Read the Node package README or Python package README for the full beta API.