How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Anchorage Digital

Anchorage Digital Atlas Settlement Network API

The Atlas Settlement Network API from Anchorage Digital — 9 operation(s) for atlas settlement network.

Documentation Provider Profile APIs.io OpenAPI GitHub

Anchorage Digital Atlas Settlement Network API is one of 28 APIs that Anchorage Digital publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Atlas Settlement Network. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 11 operations across 9 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.anchorage-staging.com/v2.

11 operations 9 paths 21 schemas 6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.anchorage.com/v2
Authentication
API Key
Contact
api@anchorage.com
Resource Areas
1

Authentication & Security 1

Anchorage Digital Atlas Settlement Network API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Access-Key (Api-Access-Key). By default, every request must be authenticated.

  • Api-Access-Key — An API key associated with a security role

Paths & Operations 11

Across 9 paths, the API surfaces 11 operations — 6 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Atlas Settlement Network 11
POST
/atlas/settlements
Propose a settlement
proposeSNSettlement 2 params body → 201400401403429500
GET
/atlas/settlements
List settlements
getSNSettlements 2 params → 200401403429500
POST
/atlas/settlements/{settlementId}/reject
Reject a settlement proposal
rejectSNSettlement 3 params → 200400401403404409429500
POST
/atlas/settlements/{settlementId}/authorize
Authorize a settlement
authorizeSNSettlement 4 params body → 200400401403404409429500
POST
/atlas/settlements/{settlementId}/accept
Accept a settlement
acceptSNSettlement 3 params body → 200400401403404409429500
GET
/atlas/settlements/{settlementId}
Get a settlement by ID
getSNSettlement 1 param → 200401403404429500
POST
/atlas/directory/counterparties
Propose a trusted counterparty
proposeSNTrustedCounterparty 2 params body → 201400401403429500
GET
/atlas/directory/counterparties
List trusted counterparties
getSNTrustedCounterparties 3 params → 200401403429500
GET
/atlas/directory/counterparties/{counterpartyId}
Get a counterparty by ID
getSNTrustedCounterparty 2 params → 200401403404429500
GET
/atlas/directory/participants/{participantId}
Get a participant by ID
getSNParticipant 1 param → 200401403404429500
GET
/atlas/directory/participants
List participants
getSNParticipants 2 params → 200401403429500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are SNSettlementProposal (8 properties), SNSettlement (6 properties), SNSettlementSide (6 properties), SNTrustedCounterparty (4 properties). Each schema is shown below with its type and property counts.

SNParticipantTier
string
SNParticipantResponse
object
1 property 1 required
ErrorDetails
object
2 properties 2 required
SNWalletAmount
object
3 properties 2 required
SNSettlementAuthorization
object
3 properties 3 required
SNParticipantsResponse
object
2 properties 2 required
SNSettlementResponse
object
1 property 1 required
Page
object
Pagination info
1 property
SNSettlementProposal
object
8 properties 5 required
SNSettlementState
string
SNProposeSettlementResponse
object
1 property 1 required
SNTrustedCounterpartyResponse
object
1 property 1 required
SNSettlementSide
object
6 properties 1 required
SNTrustedCounterpartyProposal
object
4 properties 3 required
SNParticipant
object
4 properties 3 required
SNTrustedCounterpartiesResponse
object
2 properties 2 required
SNSettlement
object
A settlement is a proposal to move assets between wallets owned by two participants. When the settlement status is ActionNeeded, refer to your participant's se…
6 properties 6 required
ErrorType
string
The type of error returned.
SNTrustedCounterparty
object
4 properties 3 required
SNSettlementsResponse
object
2 properties 2 required
SNAcceptSettlementRequest
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-atlas-settlement-network-api-openapi.yml Raw ↑

Other APIs Anchorage Digital publishes across the network.

Anchorage Digital Addresses API
AE Profile APIs.io
Anchorage Digital AML API
AE Profile APIs.io
Anchorage Digital API Key API
AE Profile APIs.io
Anchorage Digital Asset Types API
AE Profile APIs.io
Anchorage Digital Asset Types & Networks API
AE Profile APIs.io
Anchorage Digital Balances API
AE Profile APIs.io
Anchorage Digital Collateral Management API
AE Profile APIs.io
Anchorage Digital Deposit Attribution API
AE Profile APIs.io
Anchorage Digital Fiat Banking Operations API
AE Profile APIs.io
Anchorage Digital Onboarding API
AE Profile APIs.io
Anchorage Digital Stablecoins API
AE Profile APIs.io
Anchorage Digital Statements API
AE Profile APIs.io
#Atlas Settlement Network
← Back to A APIs
API Details
ID
anchorage:anchorage-atlas-settlement-network-api
Base URL
https://api.anchorage.com/v2
Docs
https://docs.anchorage.com/knowledge-base/api-reference/introduction
Provider
Anchorage Digital
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=anchorage-atlas-settlement-network-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/anchorage-atlas-settlement-network-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Anchorage Digital Atlas Settlement Network API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.