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

Ultravioleta DAO Account API

User account management and preferences.

Ultravioleta DAO Account API is one of 40 APIs that Ultravioleta DAO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

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

Requests are made against 2 base URLs: https://api.execution.market, http://localhost:8000.

9 operations 8 paths 13 schemas 2 DELETE3 GET2 PATCH1 POST1 PUT

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.execution.market
Authentication
API Key, API Key, OAuth 2.0, API Key, API Key
License
Resource Areas
1

Authentication & Security 5

Ultravioleta DAO Account API declares 5 security schemes for authenticating requests. An API key is passed in the header as Signature-Input (erc8128). An API key is passed in the header as X-EM-Session (walletSession). It supports OAuth 2.0 (oauthBearer) using the authorizationCode flow, exposing 9 scopes. An API key is passed in the header as X-EM-Approval (releaseApproval). An API key is passed in the header as X-Payment-Auth (x402Payment). By default, every request must be authenticated.

  • erc8128 — ERC-8128 (RFC 9421 HTTP Message Signatures). Requires the Signature + Signature-Input + Content-Digest headers, with a nonce from GET /api/v1/auth/erc8128/nonc…
  • walletSession — Signed session (walletsession). A SessionGrant this server builds at POST /api/v1/auth/session/challenge, signed by the wallet and replayed verbatim. For clien…
  • oauthBearer — OAuth 2.1 for third-party MCP clients, with no prior agreement: discover, register (or use a Client ID Metadata Document), sign in with your wallet, get a toke…
  • releaseApproval — Per-operation EIP-712 ReleaseApproval naming ONE submission. Required to approve when the principal authenticated with walletsession, because approve releases…
  • x402Payment — x402 payment authorization — the agent's signed EIP-3009 ReceiveWithAuthorization that funds the task escrow. Required on paid operations; the server never sig…

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 2 DELETE, 3 GET, 2 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Account 9

User account management and preferences.

DELETE
/api/v1/account
Delete account
delete_account_api_v1_account_delete 1 param → 200401422
GET
/api/v1/account/export
Export account data
export_account_data_api_v1_account_export_get 1 param → 200401422
PATCH
/api/v1/account/solana-payout-address
Bind a Solana payout address
set_solana_payout_address_api_v1_account_solana_payout_address_patch 1 param body → 200400401403404422
PATCH
/api/v1/account/wallet
Change wallet address
update_wallet_address_api_v1_account_wallet_patch 1 param body → 200400401403404409422
POST
/api/v1/account/link-wallet
Link wallet to current session
link_wallet_to_session_api_v1_account_link_wallet_post 1 param body → 200400401403503422
PUT
/api/v1/account/dx402-key
Declare your DX402 decryption key
set_dx402_key_api_v1_account_dx402_key_put body → 200400401422
GET
/api/v1/account/dx402-key/{wallet_address}
Read a wallet's declared DX402 key
get_dx402_key_api_v1_account_dx402_key__wallet_address__get 1 param → 200422
GET
/api/v1/account/paybox-link
PayBox link of the authenticated wallet
get_paybox_link_api_v1_account_paybox_link_get → 200
DELETE
/api/v1/account/paybox-link
Unlink PayBox from the authenticated wallet
delete_paybox_link_api_v1_account_paybox_link_delete → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are AccountExportResponse (7 properties), UpdateWalletResponse (5 properties), ValidationError (5 properties), SolanaPayoutAddressResponse (5 properties). Each schema is shown below with its type and property counts.

Dx402KeyRequest
object
Declare the PUBLIC key your durable evidence should be sealed to.
2 properties 1 required
AccountExportResponse
object
GDPR data export payload (GET /account/export). Documentation-only: the endpoint returns a JSONResponse (with a Content-Disposition attachment header), which b…
7 properties 6 required
UpdateWalletResponse
object
Response for a wallet address change.
5 properties 4 required
ErrorResponse
object
Error response model.
3 properties 2 required
AccountDeleteResponse
object
Response for account deletion (anonymization).
1 property 1 required
SolanaPayoutAddressResponse
object
Response for a Solana payout address binding.
5 properties 4 required
ValidationError
object
5 properties 3 required
UpdateWalletRequest
object
Request to change the executor's wallet address. The new wallet must sign the exact message to prove ownership. The message MUST follow the format "Execution M…
3 properties 3 required
LinkWalletResponse
object
Response for linking a wallet to the current session.
4 properties 4 required
HTTPValidationError
object
1 property
LinkWalletRequest
object
Request to link the caller's wallet to their current Supabase session. Binds executors.userid to the JWT sub so worker-auth endpoints can resolve the executor.…
4 properties 1 required
SolanaPayoutAddressRequest
object
Bind a Solana payout address to the authenticated executor. This is NOT an identity change. The executor keeps its EVM walletaddress — auth (ERC-8128, secp256k…
3 properties 3 required
Dx402KeyResponse
object
The declared key currently on file for a wallet.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

execution-market-account-api-openapi.yml Raw ↑

Other APIs Ultravioleta DAO publishes across the network.

Execution Market MCP Server
Execution Market A2A Agent
Ultravioleta DAO A2A API
Ultravioleta DAO A2A Discovery API
Ultravioleta DAO A2A Protocol API
Ultravioleta DAO Agent Auth API
Ultravioleta DAO Arbiter As A Service API
Ultravioleta DAO Audit API
Ultravioleta DAO Disputes API
Ultravioleta DAO ENS API
Ultravioleta DAO Escrow API
Ultravioleta DAO Evidence API
Where this information came from

This is an independent, third-party profile of Ultravioleta DAO Account 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.