Developers · Preview

A small surface,
done properly.

REST, webhooks and MCP in front of a policy layer and a DSP adapter. This page is a design preview. Shapes are illustrative and will change before release.

agent-to-agent flowPreview
  Your DSP / traders                   Disolv                          Seller agents
        │                                   │                                  │
        │── POST /v1/briefs ───────────────▶│                                  │
        │◀─ plan (draft, explainable) ──────│                                  │
        │                                   │── discover + request proposal ──▶│  AAMP
        │                                   │◀─ proposals (agent-readable) ────│
        │                                   │── negotiate within policy ──────▶│
        │◀─ approval.required (diff) ───────│                                  │
        │── POST /v1/approvals/{id} ───────▶│                                  │
        │◀─ deal.accepted · campaign.draft ─│                                  │
REST API

Resources you would expect.

Typed, idempotent, evented. Every state change can be delivered as a webhook.

  • /v1/briefs create and update briefs
  • /v1/plans draft plans and their rationale
  • /v1/deals discovery, proposals and negotiation state
  • /v1/approvals pending decisions with diffs
  • /v1/policies limits and autonomy level
  • /v1/audit the immutable action log
GET /v1/approvals/apr_123Preview
# Illustrative response
{
  "id": "apr_123",
  "type": "deal.out_of_policy",
  "reason": "price_above_ceiling",
  "proposal": { "seller": "agent://seller.example" },
  "policy": "pol_default_approve_all",
  "actions": ["approve", "counter", "reject"]
}
mcp · toolsPreview
create_brief
draft_plan
discover_sellers
request_proposal
negotiate_deal
check_policy
request_approval
create_draft_campaign
MCP

Bring your own agents.

Disolv exposes its capabilities as MCP tools, so the agents and clients you already run can use them. Side effects always pass through the policy layer first.

DSP adapter

One narrow contract.

A DSP implements a small adapter interface for campaigns, line items and deals. We ship a reference adapter and work with design partners on the first real ones.

adapter.tsPreview
interface DspAdapter {
  createCampaign(draft: CampaignDraft): Promise<CampaignRef>
  createLineItem(draft: LineItemDraft): Promise<LineItemRef>
  registerDeal(deal: AcceptedDeal): Promise<DealRef>
  getStatus(ref: Ref): Promise<Status>
}

Want to shape the API?

Design partners get a direct line to the team and a say in the adapter interface and policy model.

Request early access →hello@disolv.com