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 Workers API

Worker (executor) registration, profiles, and management.

Ultravioleta DAO Workers 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 Workers. 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 17 operations across 15 paths, and defines 12 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.

17 operations 15 paths 12 schemas 9 GET1 PATCH5 POST2 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 Workers 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 17

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

Workers 17

Worker (executor) registration, profiles, and management.

POST
/api/v1/workers/register
Register Worker
register_worker_api_v1_workers_register_post body → 200400500422
GET
/api/v1/workers/world-status
Check World Human Verification
get_world_status_api_v1_workers_world_status_get 1 param → 200400500422
GET
/api/v1/workers/tasks/{task_id}/my-submission
Get My Submission
get_my_submission_api_v1_workers_tasks__task_id__my_submission_get 3 params → 200404422
GET
/api/v1/workers/tasks/{task_id}/geo-reference
Get Task Geo Reference
get_task_geo_reference_api_v1_workers_tasks__task_id__geo_reference_get 3 params → 200403404422
GET
/api/v1/submissions/{submission_id}
Get Submission Detail
get_submission_detail_api_v1_submissions__submission_id__get 2 params → 200403404422
POST
/api/v1/tasks/{task_id}/apply
Apply To Task
apply_to_task_api_v1_tasks__task_id__apply_post 2 params body → 200400403404409422
POST
/api/v1/tasks/{task_id}/withdraw
Withdraw From Task
withdraw_from_task_api_v1_tasks__task_id__withdraw_post 2 params body → 200401403404409502503422
POST
/api/v1/tasks/{task_id}/submit
Submit Work
submit_work_api_v1_tasks__task_id__submit_post 2 params body → 200400403404409422
GET
/api/v1/payments/events
Get Payment Events
get_payment_events_api_v1_payments_events_get 6 params → 200422
PUT
/api/v1/workers/social-links
Update Social Links
update_social_links_api_v1_workers_social_links_put 1 param body → 200400401422
PUT
/api/v1/workers/service-area
Declarar la zona de operación
update_service_area_api_v1_workers_service_area_put 1 param body → 200400401503422
GET
/api/v1/workers/service-area
Leer la zona de operación propia
get_service_area_api_v1_workers_service_area_get 1 param → 200401422
GET
/api/v1/workers/{wallet}/reputation-network
Get Reputation Network Preference
get_reputation_network_api_v1_workers__wallet__reputation_network_get 1 param → 200400422
PATCH
/api/v1/workers/{wallet}/reputation-network
Set Reputation Network Preference
update_reputation_network_api_v1_workers__wallet__reputation_network_patch 2 params body → 200400401403409429422
POST
/api/v1/executors/register
Register Worker
register_executor_api_v1_executors_register_post body → 200422500
GET
/api/v1/executors/{executor_id}/tasks
Get Worker Tasks
get_my_tasks_api_v1_executors__executor_id__tasks_get 2 params → 200500422
GET
/api/v1/executors/{executor_id}/stats
Get Worker Statistics
get_executor_stats_api_v1_executors__executor_id__stats_get 1 param → 200404500422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ValidationError (5 properties), WorkerSubmissionRequest (4 properties), UpdateServiceAreaRequest (4 properties), WorkerRegisterRequest (3 properties). Each schema is shown below with its type and property counts.

UpdateServiceAreaRequest
object
La zona de operación que el worker declara (Chamba F2.2). Dos formas de decir lo mismo, y el resultado guardado es siempre UN polígono (migración 217): centerl…
4 properties
UpdateReputationNetworkRequest
object
Request to set the chain where the user's ERC-8004 reputation is written (decoupled from the payment chain; ratee-driven).
1 property 1 required
WorkerSubmissionRequest
object
Request model for worker submitting work.
4 properties 2 required
ErrorResponse
object
Error response model.
3 properties 2 required
WorkerWithdrawRequest
object
Request model for the assigned worker stepping down from a task.
2 properties 1 required
ExecutorRegistration
object
2 properties 1 required
ValidationError
object
5 properties 3 required
WorkerRegisterRequest
object
Request model for registering a worker by wallet address.
3 properties 1 required
HTTPValidationError
object
1 property
UpdateSocialLinksRequest
object
Request to add or update a social link on executor profile.
2 properties 2 required
WorkerApplicationRequest
object
Request model for worker applying to a task.
3 properties 1 required
SuccessResponse
object
Generic success response.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

execution-market-workers-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 Account 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
Where this information came from

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