Agentic Platform

The @agentic/platform-emails package contains the internal email templates used by the Agentic platform.

Note: This is a private package. It is primarily intended for developers contributing directly to the Agentic platform rather than for general consumption by third-party developers.

Agentic is a platform described as 'RapidAPI for LLM tools'. It provides a curated marketplace of high-quality tools specifically optimized for LLM and Model Context Protocol (MCP) use cases (referred to as 'Agentic UX').

Key capabilities include:

• MCP Gateway: A fast gateway powered by Cloudflare's edge network that supports both consuming and publishing MCP servers and OpenAPI services.
• Monetization: Allows developers to publish MCP servers or OpenAPI services and charge for usage via Stripe.
• TypeScript Integration: Provides one-line integrations for major TypeScript LLM SDKs.
• Usage-based Billing: Most tools use Stripe for usage-based billing.
• Versioning: Tools follow semantic versioning (semver).

If a customer does not provide an API key for an MCP or HTTP call, Agentic's MCP Gateway defaults the request to the following state:

• isCustomerSubscriptionActive is set to false.
• The customer is assigned to your project's free pricing plan.

Unauthenticated requests are subject to the rate limits defined for your project's free plan. Ensure you have configured these limits to protect your origin server from abuse.

When configuring rate limits, you must choose between two enforcement modes:

1. approximate (Default): This mode is optimized for performance. Requests are allowed to proceed immediately, and the rate limit is enforced asynchronously in the background. Use this when low latency is more important than perfect adherence to the limit.

2. strict: This mode is optimized for precision. Customer requests are blocked until the current limit has been confirmed. Use this when it is critical that customers never exceed their allocated quota, acknowledging that this will increase latency for every request.

Agentic manages Stripe resources (products, prices, meters, subscriptions, customers, etc.) automatically based on your declarative JSON-based pricing configuration in agentic.config.ts.

When you deploy changes to your pricing configuration, Agentic performs a lazy upsert of the related Stripe resources. If a resource has not changed between deployments, Agentic continues to use the existing Stripe resource to ensure existing customer subscriptions are not disrupted.

Agentic uses a separation of concerns between its MCP Gateway and your remote origin server. This architecture allows you to author and host your MCP servers or OpenAPI services in any language or framework and deploy them to any cloud provider.

Note: Currently, Agentic only supports remote origin servers. If you wish to host your origin server directly on Agentic's infrastructure, you must contact their team.

Cache keys for tool calls are generated by normalizing the tool call's input. This applies regardless of whether the tool call is made via HTTP POST, HTTP GET, or MCP.

To ensure consistency, tool call arguments are hashed using a stable, deterministic JSON serialization algorithm. This means tool calls with identical JSON inputs will always result in identical cache keys.

Agentic provides hosted authentication for your projects. The user lifecycle follows this flow:

1. Users sign into Agentic using supported methods (currently Email & password or GitHub).
2. Users subscribe to your project via Stripe.
3. Upon subscription, users are issued an API key.
4. Users use this API key for their tool calls.

The Agentic MCP gateway tracks all usage of your project by monitoring these API keys. When a request reaches your origin server, the gateway passes customer authentication and subscription information via Origin Metadata.

The Agentic platform uses a hierarchical identifier system for projects, deployments, and tools.

Project Identifier

Format: @username/project-slug or @team-slug/project-slug. Example: @agentic/search

Deployment Identifier

Appends a deployment scope to a Project Identifier:

• ${projectIdentifier}: Implicitly uses @latest.
• ${projectIdentifier}@latest: The most recently published deployment.
• ${projectIdentifier}@dev: The most recently pushed deployment.
• ${projectIdentifier}@deploymentHash: A specific deployment hash.
• ${projectIdentifier}@version: A specific published deployment using semver.

Tool Identifier

Appends a tool name to a Deployment Identifier: Format: ${deploymentIdentifier}/tool_name Examples:

• @agentic/search/search
• @agentic/search@latest/search
• @agentic/search@1.0.0/search

Use the toolConfigs array in your configuration to override default gateway behavior for specific tools. This allows you to disable tools, set custom rate limits, customize metered billing usage reporting, and define behavior overrides for different pricing plans.

Note that tool-specific configurations override the defaults defined in your pricing plans. If a tool is present on your origin server but not listed in toolConfigs, it will follow the default Agentic MCP gateway behavior.

import { defineConfig } from '@agentic/platform'

export default defineConfig({
  // ...
  toolConfigs: [
    {
      name: 'my-tool',
      // configuration options go here
    }
  ]
})

Agentic allows you to turn any remote MCP server or OpenAPI service into a paid MCP product by using the Agentic MCP Gateway as a public proxy.

The workflow follows three main steps:

1. Create your origin server: Host your own MCP server or OpenAPI service anywhere using any language or framework.
2. Publish to Agentic's MCP Gateway: The Gateway acts as a proxy between your origin server and customers. It provides production-ready features including authentication, billing, rate-limiting, caching, usage tracking, and versioning. It also ensures instant compatibility with major LLM SDKs and MCP clients.
3. Share and monetize: Once published, you share the public URL with customers. They can subscribe via Stripe, and Agentic uses Stripe Connect to facilitate payments to your bank.