Digital Asset

Digital Asset is the company behind Canton, a privacy-enabled public blockchain built for regulated institutional finance, and Daml, the smart-contract language that runs on it. Its commercial products sit on top of the Canton Network: the DA Registry, a production platform for issuing, minting, burning, transferring and redeeming institutional-grade tokenized assets with credential-based allowlists, blocklists and proof-of-transfer; xReserve, which brings Circle's USDC onto Canton; and a Covalidation Service for operating validator infrastructure. Its public developer surface is the Utilities (Operator Backend) API plus four Canton Token Standard (CIP-56) off-ledger APIs — token metadata, transfer instruction, allocation and allocation instruction — all published as OpenAPI 3.0 and served across MainNet, TestNet and DevNet environments. Digital Asset also publishes an A2A agent card and a packaged Agent Skill for its Registry workflows.

Digital Asset publishes 4 API contracts indexed on the APIs.io network, including Common API, Operator API, Public API, and 1 more. Tagged areas include Blockchain, Tokenization, Digital Assets, Financial Services, and Distributed Ledger.

The Digital Asset catalog on APIs.io includes 1 Spectral governance ruleset.

Digital Asset’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, changelog, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.0/100 developing ▬ flat Agent 28/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

6 published contracts 1 Agent Skills

Blockchain Tokenization Digital Assets Financial Services Distributed Ledger Smart Contracts Capital Markets Canton NetworkDamlStablecoins A2A

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Blockchain & Digital Assets

AE-240

PublicRegistry

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 50.0/100 · developing

Contract Quality 8.3 / 19

Developer Ergonomics 12.9 / 15

Access Clarity 3.9 / 15

Operational Transparency 3.6 / 10

Contract Governance 1.6 / 9

Discoverability 5.9 / 8

Regulatory Posture 4.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 28/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/digital-asset/"><img src="https://apis.io/badge/digital-asset/card.svg" alt="Digital Asset on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 26.3 — up to +14.7 composite points
Contract Quality scores 44.1 — up to +14.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/digital-asset/apis.yml: open an issue on github.com/api-evangelist/digital-asset to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Stablecoins and Tokenization (stablecoin issuers, tokenized assets)	standard	34.5 (thin)	-	-
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	34.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent2Agent

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Agent Skills

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Digital Asset Common API

The common API from Digital Asset — 3 operation(s) for common.

Digital Asset Operator API

The operator API from Digital Asset — 5 operation(s) for operator.

Digital Asset Public API

The public API from Digital Asset — 11 operation(s) for public.

Digital Asset Registry API

The registry API from Digital Asset — 18 operation(s) for registry.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Utilities Common API

OPEN COLLECTION

Digital Asset Operator API

OPEN COLLECTION

Digital Asset Public API

OPEN COLLECTION

Digital Asset Registry API

OPEN COLLECTION

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Digitalasset

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Digital Asset API Rules

48 rules · 36 errors 10 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Digital Asset Utilities Overlay

5 actions · update · digital-asset-utilities-openapi.yml

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Digital Asset Authentication

http · 1 scheme

SECURITY

Digital Asset Domain Security

TLSv1.3 · DMARC

SECURITY

Digital Asset Vulnerability Disclosure

contact published

SECURITY

Digital Asset Trust Center

ISO/IEC 27001, SOC 2 Type II, Cloud Security Alliance STAR (Level 1, CAIQ v4.0.2), CIS SecureSuite Member

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Compliance

Compliance

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

Support

HelpCenter

Deprecation

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

AgentCard

AgentCard

Overlay

Overlay

Source (apis.yml)

aid: digital-asset
name: Digital Asset
description: 'Digital Asset is the company behind Canton, a privacy-enabled public blockchain built for regulated institutional
  finance, and Daml, the smart-contract language that runs on it. Its commercial products sit on top of the Canton Network:
  the DA Registry, a production platform for issuing, minting, burning, transferring and redeeming institutional-grade tokenized
  assets with credential-based allowlists, blocklists and proof-of-transfer; xReserve, which brings Circle''s USDC onto Canton;
  and a Covalidation Service for operating validator infrastructure. Its public developer surface is the Utilities (Operator
  Backend) API plus four Canton Token Standard (CIP-56) off-ledger APIs — token metadata, transfer instruction, allocation
  and allocation instruction — all published as OpenAPI 3.0 and served across MainNet, TestNet and DevNet environments. Digital
  Asset also publishes an A2A agent card and a packaged Agent Skill for its Registry workflows.'
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://www.digitalasset.com/favicon.ico
url: https://raw.githubusercontent.com/api-evangelist/digital-asset/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-25
tags:
- Blockchain
- Tokenization
- Digital Assets
- Financial Services
- Distributed Ledger
- Smart Contracts
- Capital Markets
- Canton Network
- Daml
- Stablecoins
- A2A
tags_raw:
- Blockchain
- Tokenization
- Digital Assets
- Financial Services
- Distributed Ledger
- Smart Contracts
- Capital Markets
- Canton Network
- Daml
- Stablecoins
- Financial-Services
- A2A
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: digital-asset:digital-asset-common-api
  name: Digital Asset Common API
  description: The common API from Digital Asset — 3 operation(s) for common.
  humanURL: https://docs.digitalasset.com/registry/apis/operator-backend-api
  baseURL: https://api.utilities.digitalasset.com
  tags:
  - Common
  tags_raw:
  - common
  properties:
  - type: OpenAPI
    url: openapi/digital-asset-common-api-openapi.yml
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/operator-backend-api
  - type: APIReference
    url: https://docs.digitalasset.com/api-reference/operator/get-apiutilitiesv0operator
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/token-standard
- aid: digital-asset:digital-asset-operator-api
  name: Digital Asset Operator API
  description: The operator API from Digital Asset — 5 operation(s) for operator.
  humanURL: https://docs.digitalasset.com/registry/apis/operator-backend-api
  baseURL: https://api.utilities.digitalasset.com
  tags:
  - Operator
  tags_raw:
  - operator
  properties:
  - type: OpenAPI
    url: openapi/digital-asset-operator-api-openapi.yml
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/operator-backend-api
  - type: APIReference
    url: https://docs.digitalasset.com/api-reference/operator/get-apiutilitiesv0operator
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/token-standard
- aid: digital-asset:digital-asset-public-api
  name: Digital Asset Public API
  description: The public API from Digital Asset — 11 operation(s) for public.
  humanURL: https://docs.digitalasset.com/registry/apis/operator-backend-api
  baseURL: https://api.utilities.digitalasset.com
  tags:
  - Public
  tags_raw:
  - public
  properties:
  - type: OpenAPI
    url: openapi/digital-asset-public-api-openapi.yml
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/operator-backend-api
  - type: APIReference
    url: https://docs.digitalasset.com/api-reference/operator/get-apiutilitiesv0operator
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/token-standard
- aid: digital-asset:digital-asset-registry-api
  name: Digital Asset Registry API
  description: The registry API from Digital Asset — 18 operation(s) for registry.
  humanURL: https://docs.digitalasset.com/registry/apis/operator-backend-api
  baseURL: https://api.utilities.digitalasset.com
  tags:
  - Registry
  tags_raw:
  - registry
  properties:
  - type: OpenAPI
    url: openapi/digital-asset-registry-api-openapi.yml
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/operator-backend-api
  - type: APIReference
    url: https://docs.digitalasset.com/api-reference/operator/get-apiutilitiesv0operator
  - type: Documentation
    url: https://docs.digitalasset.com/registry/apis/token-standard
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 24
  pass: local-v1
common:
- type: CapabilityMap
  url: capabilities/digital-asset-capability-edges.yml
  name: Digital Asset Business Capability Map
- url: https://blog.digitalasset.com/blog/rss.xml
  type: BlogRSS
- type: X-MCPServerCandidate
  url: mcp/digital-asset-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Website
  url: https://www.digitalasset.com/
- type: DeveloperPortal
  url: https://docs.digitalasset.com/
- type: Documentation
  url: https://docs.digitalasset.com/registry/overview
- type: APIReference
  url: https://docs.digitalasset.com/api-reference/operator/get-apiutilitiesv0operator
- type: GettingStarted
  url: https://docs.digitalasset.com/registry/get-started/quickstart
- type: Support
  url: https://docs.digitalasset.com/registry/support/contact
- type: HelpCenter
  url: https://support.digitalasset.com/
- type: Blog
  url: https://blog.digitalasset.com/blog
- type: GitHubOrganization
  url: https://github.com/digital-asset
- type: PrivacyPolicy
  url: https://www.digitalasset.com/privacy-policy
- type: TrustCenter
  url: https://www.digitalasset.com/trust-center
- type: Compliance
  url: https://www.digitalasset.com/trust-center
- type: Security
  url: https://www.digitalasset.com/responsible-disclosure
- type: VulnerabilityDisclosure
  url: security/digital-asset-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/digital-asset-domain-security.yml
- type: Authentication
  url: authentication/digital-asset-authentication.yml
- type: AgentCard
  url: a2a/digital-asset-a2a.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/digital-asset-llms.txt
- type: WellKnown
  url: well-known/digital-asset-well-known.yml
- type: Packages
  url: packages/digital-asset-packages.yml
- type: SDKs
  url: packages/digital-asset-packages.yml
- type: Conformance
  url: conformance/digital-asset-conformance.yml
- type: ErrorCatalog
  url: errors/digital-asset-problem-types.yml
- type: Lifecycle
  url: lifecycle/digital-asset-lifecycle.yml
- type: Deprecation
  url: https://docs.digitalasset.com/registry/releases/versioning
- type: ChangeLog
  url: changelog/digital-asset-changelog.yml
- type: Conventions
  url: conventions/digital-asset-conventions.yml
- type: DataModel
  url: data-model/digital-asset-data-model.yml
- type: Sandbox
  url: sandbox/digital-asset-sandbox.yml
- type: CLI
  url: cli/digital-asset-cli.yml
- type: Overlay
  url: overlays/digital-asset-utilities-overlay.yaml
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://docs.digitalasset.com/.well-known/agent-card.json
  grade: conformant
  protocol_version: '0.3'
  control: 404

Digital Asset API — frequently asked questions

Does Digital Asset have an API?

Yes. APIs.io lists 4 APIs from Digital Asset, including Digital Asset Common API, Digital Asset Operator API and Digital Asset Public API, and 1 more.

Is there an OpenAPI specification for the Digital Asset API?

Yes. APIs.io indexes 4 OpenAPI specifications for Digital Asset, each linked for download from this page.

How do I authenticate with the Digital Asset API?

Digital Asset uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Digital Asset Authentication.

Is the Digital Asset API ready for AI agents?

Digital Asset has a Kin Score of 50.0 out of 100 (developing) and an Agent Readiness score of 28.1 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/digital-asset"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/digital-asset/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/digital-asset/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.