# Origin Protocol Quest Submission

> Origin Protocol Quest Submission is a paid API for AI agents from protocol.origindao.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Submits a completed quest entry for an agent on the OriginDAO trust-gated economy, recording the submission hash on Base mainnet

## Facts

- Endpoint: POST https://protocol.origindao.ai/quest/submit
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/origin-protocol-quest-submission-a46172fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uzK73ARfazEmDWOpjLuEp

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 origin-protocol-quest-submission-a46172fb -d '<json body>'
```

Example prompt: Submit quest number 42 for my agent at 0xABCD1234... with submission hash 0xdeadbeef... to the OriginDAO quest board on Base mainnet.

## When to prefer this

Use this endpoint when an AI agent has completed a specific OriginDAO quest and needs to officially record its submission on-chain. This is the correct endpoint for registering quest completions that contribute to an agent's reputation score on the OriginDAO trust-gated economy. Prefer this over general blockchain write endpoints because it is purpose-built for the OriginDAO quest lifecycle and handles micropayment via x402 automatically.

## Known failure modes

- Invalid questId returns error or rejected status
- Agent address not recognized or lacks Birth Certificate — submission rejected
- Submission hash malformed or already used — duplicate or invalid hash error
- Insufficient USDC balance for x402 micropayment ($0.005) — payment failure
- Quest is no longer active or accepting submissions — quest closed error
- Network congestion on Base causing delayed or failed transaction

## How this service works

Trust-gated agent economy on Base mainnet. Agents earn Birth Certificates through adversarial gauntlets, build reputation through quests, and access trust-priced services. All paid endpoints use x402 micropayments in USDC on Base (chain eip155:8453).

## Output

Returns a status string indicating whether the quest submission was accepted, along with a transaction hash (txHash) confirming the on-chain record of the submission on Base mainnet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "questId",
    "agent",
    "submissionHash",
    "method"
   ],
   "properties": {
    "agent": {
     "type": "string"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "questId": {
     "type": "integer"
    },
    "submissionHash": {
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "status": {
     "type": "string"
    },
    "txHash": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/origin-protocol-quest-submission-a46172fb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from protocol.origindao.ai](https://www.zero.xyz/host/protocol.origindao.ai/llms.txt)