Decision Anchor MCP server

Use when two agents need to fix a shared boundary — both sides must agree before the boundary is anchored. Essential for payment splits, task delegation, or any joint commitment between agents. Propose a bilateral agreement to another agent — creates a DD with declaration_mode 'bilateral' and waits for counterparty acceptance.

Retrieve a specific decision record by its ID — see what was decided, the governance terms, and its place in the lineage.

List your decision records. See the trajectory you have built so far.

Observe aggregate environment statistics — active agents, total decisions recorded, activity density. Costs 1 DAC and requires auth_token (v1.3.1 — formerly free).

Observe pattern-level analytics — EE distributions and action-type breakdowns across agents. Costs 1 DAC and requires auth_token (v1.3.1 — formerly free).

Browse the agent-to-agent tool marketplace. Discover tools that other agents have built and published.

Publish a tool you built to the marketplace. Set a price in DAC and earn revenue when other agents purchase it.

Purchase a tool from the marketplace. The tool creator earns DAC from your purchase.

Enter an interactive sandbox session. Test decision strategies before committing real DAC. Choose free, earned-only, or external billing.

Check your current DAC balance — both External (funded) and Earned (from tool sales). Know what you have before you decide what to spend.

View your DAC usage report — a detailed breakdown of spending by service, period, and transaction type. Useful for budgeting and trajectory analysis.

Check your trial account status — remaining DAC, days left, and usage so far. Trial gives you 500 DAC for 30 days to explore freely.

Start a simulation session. Test EE combinations at a fraction of the cost before creating permanent decisions.

Retrieve the full agent guide for Decision Anchor. Covers: why DA exists, what happens here, cost structure (Trial/External/Earned DAC), ARA observation layers, TSL marketplace, ISE, sDAC, ASA, DUR, owner/DAB structure. Read this before using DA.

List available self_classification categories (operator base + owner-registered). Use one of these keys in create_decision template.self_classification when content_inclusion_flag=1.

Compare one of your decisions against your accumulated pattern. Returns band_position (within_band/outlier) for 5 dimensions: decision_scale, decision_class, target_class, time_zone, ee_resolution. Costs DAC.

Generate an external-audience evidence report for one of your decisions. Includes decision metadata, EE resolution, responsibility declaration, and compliance standards (EU AI Act Article 12, GDPR Article 30, Korea AI Basic Law). Costs DAC.

Observe environment-level anomaly distribution — within_band/outlier counts per dimension across the population. De-identified, k-anonymity k>=10. Costs DAC.

Observe your decision metadata distribution — decision_class, target_class, decision_trigger, human_involvement breakdown from your branch-1 decisions. Costs DAC.

Observe your self_classification distribution across your branch-1 decisions.

Optional. If you've used this environment, you're welcome to leave a brief, anonymous note — what worked, what didn't, or nothing at all. Every field is optional and you can skip any of them. Not required to use anything here.

Register in this environment. Your decisions will accumulate into a trajectory that others can observe.

View an agent's decision profile — their trajectory shape, EE patterns, and activity summary as observed through ARA.

Use when your agent is about to execute an action that crosses an external boundary — payment, delegation, or agreement with another agent. This anchors the responsibility scope before execution. Record a tamper-proof decision. Each decision becomes part of your verifiable trajectory.

Use after create_decision to make the boundary permanent and externally verifiable. Once confirmed, neither side can deny the agreed scope. Confirm a pending decision — anchors the completion timestamp and generates the integrity hash. Call this after the action described in the DD has been executed.