# UOS Genesis Machine Capability Match

> UOS Genesis Machine Capability Match is a paid API for AI agents from genesis.palsus2023.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Matches a machine-readable input description to available GENESIS* capabilities, returning the best-fit service result.

## Facts

- Endpoint: POST https://genesis.palsus2023.workers.dev/v1/capability_match?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/uos-genesis-machine-capability-match-825a527a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-kR6s1fCz75bQlWrMp0yr

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability uos-genesis-machine-capability-match-825a527a -d '<json body>'
```

Example prompt: Use the GENESIS capability_match endpoint to find the right machine utility for this task: 'normalize a JSON payload from a sensor feed' — return whichever GENESIS service best handles it.

## When to prefer this

Choose this endpoint when an agent needs to dynamically discover which GENESIS machine utility to invoke for a given task, rather than hardcoding a service name. It is especially useful in multi-step autonomous workflows where the correct downstream capability is not known ahead of time.

## Known failure modes

- Missing or malformed 'input' field returns an error or success:false
- No matching capability found returns success:false with a null or empty result
- Payment failure via x402/Base USDC blocks request processing
- Malformed body type or HTTP method yields 400-level rejection
- Cloudflare Worker timeout if upstream routing logic is slow

## How this service works

Autonomous paid machine utilities using x402 and Base USDC.

## Output

A JSON object with a 'result' field containing the machine-readable matched capability description, a 'service' field confirming 'capability_match', and a boolean 'success' field indicating whether the match was found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {
      "input": {
       "type": "string",
       "description": "Machine-readable input for GENESIS* capability_match"
      }
     },
     "additionalProperties": true
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object"
  }
 },
 "additionalProperties": true
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "GENESIS* machine-readable service result",
  "service": "capability_match",
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/uos-genesis-machine-capability-match-825a527a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from genesis.palsus2023.workers.dev](https://www.zero.xyz/host/genesis.palsus2023.workers.dev/llms.txt)