A growing ecosystem of REST API tools is emerging around platforms named "Foundry," enabling developers to build external integrations and automate various functions. This includes offerings from Microsoft Foundry and the virtual tabletop environment Foundry VTT, each providing distinct methods for interaction.
![Foundry REST API - a tool/library for developers to create external integrations [system agnostic] - 1](https://cdn.gameofhost.com/image.php?q=BcHRDcAgCAXAier7dxuCBEmqEKD79253R00g6KXbloP9YDkXUsq_ZClsPxKkAit_NG2NuPoD)
Microsoft Foundry, as detailed in recent documentation, highlights its REST API for scenarios where native connectors are absent. Developers are guided to use an api-key for authentication, with resource endpoints typically following the pattern https://{resource}.services.ai.azure.com. For OpenAI compatibility, the endpoint openai.azure.com is noted. Recent publications also indicate Microsoft Foundry's efforts to connect OpenAPI tools to its agents, suggesting a structured approach to defining API interactions for agent-based functionalities. API key authentication here is managed through distinct "security schemes" per OpenAPI tool, with a "project connection name" acting as a placeholder for the authentication mechanism.
Read More: How to check used GPU hours in 2026?
![Foundry REST API - a tool/library for developers to create external integrations [system agnostic] - 2](https://cdn.gameofhost.com/image.php?q=yygpKSi20tdPSU0tKM_MztRLzs_Vz81MLsovzk8r0XfLL81LKarU9clPTszRz0_XzcxNTE_VK8hLty8AMmzNAA)
Separately, Foundry VTT offers a REST API through a node.js server acting as a relay. This allows fetching and interacting with "foundry world data." The system mandates an API key in the x-api-key header for requests, and many endpoints require a clientId that corresponds to a connected world. Documentation suggests using Postman and an "API Test Collection" for easier endpoint exploration. A GitHub repository, ThreeHats/foundryvtt-rest-api-relay, provides a more detailed technical blueprint. This project outlines a Relay Server, built with Node.js/Express, that connects to Foundry VTT modules via WebSocket and exposes REST endpoints. It lists potential applications such as building custom dashboards, automating game master tasks, integrating with hardware controllers, and creating bots. The project also offers guidance on self-hosting or using a public relay server, with Docker compose configurations and installation instructions for the Foundry VTT module.
Read More: Repowise Tool Uses Graph Analysis for Codebase Understanding
Developer Tooling and Interoperability
Beyond the core API functionalities, developer tooling is also surfacing. A project named foundry-dev-tools, updated on May 7, 2026, introduces the concept of FoundryContext which aggregates "API clients" and "Resources." This structure suggests a unified interface for interacting with different API endpoints, with clients like CompassClient making requests to specific paths like /compass/api/folders. This implies a naming convention where each API client maps to a distinct Foundry API endpoint.
Background and Context
The proliferation of these REST APIs indicates a broader trend toward enabling greater interoperability between specialized platforms and custom application development. Microsoft Foundry, as presented, appears to be integrating these API capabilities within its broader Azure AI ecosystem. Foundry VTT, a popular platform for tabletop role-playing games, is clearly leveraging APIs to extend its functionality beyond its core application, allowing for external control and data access. The use of standard protocols like REST and conventions like OpenAPI points towards an effort to adhere to common software development practices.
Read More: Arista Networks focuses on AI networking, plans faster speeds
