Foundry
Find the right API, then turn it into a governed tool.
Foundry is where implementation starts. Discover what is published, understand the contract, prove it in a sandbox, then expose it to agents as an MCP server that stays inside workspace policy.
- 01API discovery
- Browse published products, supported versions and endpoint coverage before you commit to an integration.
- 02Reference documentation
- Schemas, examples and error guidance are served as structured resources for both people and agents.
- 03Sandbox exploration
- Validate requests against realistic test data before any live call is enabled.
- 04Governed MCP servers
- Create, test, version and publish MCP servers from reviewed APIs, scoped to a single application.
From discovery to a published tool.
Each step narrows the unknowns before the next one, so nothing reaches production on assumption.
- 01
Discover the product
Start in the API catalogue and confirm the product, version and entitlement context your integration needs.
- 02
Work from the contract
Read the reference documentation, schemas and error guidance instead of guessing at request shapes.
- 03
Test in the sandbox
Run endpoint tests with scoped sandbox credentials and predictable sample data.
- 04
Publish it as a tool
Turn the reviewed API into an app-scoped MCP server with its own credential and audit trail.
Boundaries
Every Foundry credential is scoped to a workspace, application and capability set. The console may hide actions you cannot take, but the backend remains authoritative for every permission and lifecycle transition.
Start with discovery.
Browse what is published, or set up a governed MCP endpoint for your application.