Verify Proof

Description

This endpoint verifies a zero-knowledge proof submitted by an AI agent. The proof must be generated using the nonce from a valid, unexpired challenge.

Upon successful verification, the endpoint returns a confidence score (0-1) indicating the strength of the proof. A score of 0.99 indicates high confidence in the agent's identity.

Headers

Request Body

Example Request

curl -X POST https://api.zeroproofai.com/v1/verify/proof \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: your_api_key_here" \
  -d '{
    "challenge_id": "ch_7x9k2a8f3e1d9c4b",
    "proof": "a1b2c3d4e5f6...",
    "agent_signature": "sig_9x8y7z..."
  }'

// Generate proof from challenge nonce
const proof = generateProof(challenge.nonce, agentId, action);

const response = await fetch('https://api.zeroproofai.com/v1/verify/proof', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-Api-Key': 'your_api_key_here'
  },
  body: JSON.stringify({
    challenge_id: challenge.challenge_id,
    proof: proof,
    agent_signature: signature
  })
});

const result = await response.json();

if (result.verified) {
  console.log('Agent verified!', result.confidence);
  // Proceed with transaction
}

Response

Success Response (200 OK)

{
  "verified": true,
  "agent_id": "shop-bot-001",
  "action": "purchase",
  "confidence": 0.99,
  "timestamp": "2025-01-01T12:00:00Z",
  "session_id": "ch_7x9k2a8f3e1d9c4b"
}

Error Responses

400 Bad Request - Verification Failed

{
  "verified": false,
  "error": "Proof verification failed",
  "reason": "Invalid proof format"
}

400 Bad Request - Expired Challenge

{
  "error": "Challenge expired",
  "verified": false
}

400 Bad Request - Challenge Already Used

{
  "error": "Challenge already used",
  "verified": false,
  "previous_status": "verified"
}

404 Not Found

{
  "error": "Challenge not found",
  "message": "Invalid or expired challenge_id"
}

401 Unauthorized

{
  "error": "Missing API key",
  "message": "Provide API key in X-Api-Key header"
}

Verification Process

The verification process follows these steps:

1. Validates that the challenge exists and hasn't expired (5 minute TTL)
2. Checks that the challenge hasn't been used before (one-time use)
3. Verifies the cryptographic proof against the challenge nonce
4. Returns verification result with confidence score
5. Updates the challenge status to 'verified' or 'failed'

Notes

• Each challenge can only be verified once
• Challenges must be used within 5 minutes of creation
• A confidence score of 0.99 indicates successful verification
• Failed verifications are logged but don't affect API limits
• The session_id can be used to check verification status later

Next Steps

After successful verification:

• Store the session_id for audit purposes
• Proceed with the intended action (e.g., process purchase)
• Use Check Status to retrieve verification details later