Ultravioleta DAO OAuth API
The OAuth API from Ultravioleta DAO — 8 operation(s) for oauth.
Ultravioleta DAO OAuth 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 Authentication. 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 4 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 5
Ultravioleta DAO OAuth 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 — 4 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Body_consent_submit_oauth_consent_post (7 properties), ValidationError (5 properties), Body_revoke_oauth_revoke_post (2 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Ultravioleta DAO 12
Other APIs Ultravioleta DAO publishes across the network.
This is an independent, third-party profile of Ultravioleta DAO OAuth 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.