Skip to main content

Agentmark.json

The agentmark.json file is used to configure your AgentMark Cloud application.

Basic Example

agentmark.json
{
  "agentmarkPath": "/",
  "version": "2.0.0",
  "mdxVersion": "1.0",
  "builtInModels": ["gpt-4"]
}

Configuration Properties

agentmarkPath (required)

The base directory where AgentMark will look for your application’s resources including:
  • Prompt templates
  • Components
  • Datasets
  • Other AgentMark-specific resources
Default is "/", meaning AgentMark will look for the “agentmark” directory in your project root. Modify this path if you want to organize resources in a different directory structure (e.g., monorepo).

version (required)

Specifies the version of the AgentMark configuration. Useful for tracking changes and ensuring compatibility.

mdxVersion (optional)

Specifies the version of the prompt format.

builtInModels (optional)

An array of model names that are supported by AgentMark Cloud. These models are pre-configured and ready to use without additional setup.
"builtInModels": ["gpt-4", "gpt-4o-mini", "claude-3-5-sonnet"]
Additional models can be configured using the platform’s model management interface. See Model Schemas for details.

evals (optional)

An array of evaluation names that correspond to evaluations registered in your EvalRegistry. Listing evaluations here makes them available in the editor for selection when configuring prompts.
"evals": [
  "correctness",
  "hallucination",
  "relevance"
]
These names must match the evaluations you register in your code:
evalRegistry.register("correctness", (params) => {
  return { score: 0.9, label: "correct", reason: "..." };
});
Learn more: Evaluations guide

modelSchemas (optional)

Define custom model configurations with settings, pricing, and UI controls. This allows you to add models with custom parameters and cost tracking.
"modelSchemas": {
  "my-custom-model": {
    "label": "My Custom Model",
    "cost": {
      "inputCost": 0.01,
      "outputCost": 0.03,
      "unitScale": 1000000
    },
    "settings": {
      "temperature": {
        "label": "Temperature",
        "order": 1,
        "default": 0.7,
        "minimum": 0,
        "maximum": 2,
        "multipleOf": 0.1,
        "type": "slider"
      }
    }
  }
}
Learn more: Model Schemas guide

mcpServers (optional)

Configure Model Context Protocol (MCP) servers for your application. Listing servers here makes them available in the editor for selection when configuring prompts. Supports both URL/SSE and stdio server types.
"mcpServers": ["docs", "local"]
Learn more: MCP Integration guide

Have Questions?

We’re here to help! Choose the best way to reach us: