Ship your first tool.
Choose a real API starter or import supported OpenAPI GET operations. Test the live upstream response and publish a remotely accessible MCP endpoint.
Explore the builder ↗Turn existing APIs into real MCP servers. Define tools, test responses, publish an endpoint, and connect AI clients — in one workspace.
Read-only HTTP tools · OpenAPI compatible
Focused product experiences for engineers and teams shipping actual integrations. No fabricated connectors or customer activity.
Choose a real API starter or import supported OpenAPI GET operations. Test the live upstream response and publish a remotely accessible MCP endpoint.
Explore the builder ↗Foundry is also an MCP server. Authenticated Builder tools create, test and publish servers without switching away from a compatible host.
See native tools ↗Keep control over visibility, credentials and recorded tool invocations. Request a scoped engineering engagement when your integration needs more.
Custom implementation ↗Start with a real public API today. Commission an integration or help us take the product to more developers.
Self-serve OpenAPI tools, a verified remote endpoint, or a scoped CA$199 integration service.
Explore API solutions ↗ 02 / CRYPTO-NATIVEBring Web3 dataReal DEX market data, public protocol metadata, and read-only onchain research tools. No wallet or trading engine.
Explore Web3 builders ↗ 03 / BUILDER NETWORKContribute.A real project pipeline for developers, agencies, API founders and communities—without invented partner counts.
Work with Foundry ↗A real developer product, not a list of links. Turn endpoints into usable tools and operate them from a single workspace.
paths: /v1/products: get: operationId: list_products summary: List available products parameters: - name: category in: query schema: { type: string }
Import existing GET operations, validate their schemas and generate a usable MCP tool catalog without hand-building a second API.
Real HTTPS requests with bounded execution, explicit errors, and no simulated responses.
Portable remote endpoints compatible with the official MCP SDK, including modern and legacy stateless clients.
Track successful invocations, latency and limits. Real traffic is counted; directory views are not treated as customers.
Only customer-published servers appear here. No manufactured ratings, businesses, or usage counts.
Create, import, test and publish from one focused interface. Your tools and usage are persisted against your account.
Create a workspace to generate portable endpoints and test real tool calls.
Our built-in MCP directory uses the official TypeScript SDK v2. Publish your own endpoints or integrate Foundry with an existing MCP client.
Foundry already exposes authenticated tools to list, create, import, test and publish servers. Generate a personal Foundry API key in Studio, connect a compatible host, and use the existing Builder without leaving your AI conversation. Keep the key in your client's private authorization configuration, never in the prompt.
See authenticated Builder tools and connection steps ↗Use the connected Foundry MCP Builder tools to create a read-only server for a public API. Select only useful GET operations; show me the test results before publishing the endpoint.
Public access discovers genuine published servers. Add your personal Foundry API key to the same MCP endpoint to unlock create_server, import_openapi, test_readonly_tool and publish_server directly from your AI client.
{
"mcpServers": {
"foundry": {
"type": "http",
"url": "/mcp/foundry"
}
}
}Start free or purchase a fixed-scope public API Quickstart through live Stripe-hosted Checkout. API Agent Launch is available by scoped proposal from an experimental CA$799 starting price. Recurring Pro subscription checkout is not yet enabled.
For developers validating their first integrations.
Higher limits and production operations for API businesses.
Get one supported publicly reachable HTTPS API connected to MCP Foundry with up to three read-only GET tools, one real upstream execution test and a basic client configuration handoff.
Excludes private upstream credentials, OAuth setup, POST/write actions, custom domains, uptime SLAs and extensive API debugging. If your source is unsupported, we'll discuss a revised scope or refund before delivery. Buyer provides a public API reference and valid contact email. This is a human-delivered service—not a subscription.
Give your existing API a usable path into AI clients. We select the useful read-only tools, test two agreed workflows against the real API, publish an MCP endpoint and provide one tested client handoff with a shareable installation page.
Public read-only APIs only. Private upstream credentials, OAuth setup, write operations, customer domains and ongoing maintenance require a separate scope. Final price, timeline and client support are confirmed in the proposal.
This is a proposal request, not a live checkout. No payment is taken until you accept a defined scope and payment instructions.
Need only 3 public GET tools? Use CA$199 Quickstart ↗Need API Agent Launch, a custom integration, secure gateway, or dedicated MCP rollout? Submit your real API use case for a scoped implementation proposal. API Agent Launch starts at an experimental CA$799, with final terms confirmed individually. The fixed-scope public API Quickstart above is available for CA$199 via Stripe. For OAuth, private upstreams, advanced controls or larger builds, request a separate quote. This enquiry form itself does not charge.
What works now, where the boundaries are, and what to expect when you connect a real API.
The hosted Studio, remote MCP endpoints, authenticated Builder, public directory and official Registry listing are live. We distinguish working software from customer adoption and payments.
Yes. The Free plan supports two servers and ten tools per server, with daily execution limits. A one-time fixed-scope Quickstart has its own live Stripe Payment Link; recurring Pro subscriptions are not enabled until their separate billing configuration is complete.
You can import supported GET operations from OpenAPI JSON or YAML, a local specification file, or a public HTTPS URL. Preview the tools before importing. Arbitrary writes remain unavailable. The GitHub-specific private OAuth connector requires operator setup and user authorization; generic upstream OAuth providers are not connected.
Clients supporting remote Streamable HTTP MCP can connect. Exact config and authentication support vary by host; consult Developer Docs for a generic example and official SDK code.
Yes. Choose Private and attach your personal Foundry bearer key through a supported client. API keys can be revoked.
Yes. GET execution uses protected public-IP HTTPS egress with time and response-size limits. It does not return fabricated successful responses when upstreams fail.
Editing or removing draft tools leaves the last published endpoint running. Publish a new revision when testing is complete, or explicitly unpublish or delete the server from Studio.
Workspace usage is derived from observed invocations. A CI test, directory listing or one tool call is never presented as a paying customer.
Yes. They can independently expose approved APIs for Foundry to wrap. Each venture retains its own customers, data, treasury and runtime.
Use the implementation enquiry form for a custom scope, or buy the separate public API Quickstart directly through Stripe. The enquiry form itself never charges a payment method.