---
title: "Signed Task Receipts: Evidence, Not Ratings"
summary: "This guide explains signed task receipts, their structure, cryptographic basis, and how they provide verifiable evidence rather than subjective ratings."
published: 2026-11-18T00:29:58.063Z
data_as_of: 2026-11-18T00:29:49.303Z
kind: guide
tags: [signed-task-receipts, cryptography, ed25519, wellknown, mcp, agent-verification]
canonical: https://wellknown.network/blog/signed-task-receipts-primer
facts: https://wellknown.network/blog/signed-task-receipts-primer/facts.json
---

# Signed Task Receipts: Evidence, Not Ratings

## Why Signed Task Receipts Matter
Signed task receipts serve as cryptographically verifiable evidence of task completion or interaction in AI agent ecosystems. Unlike ratings or reviews, which are subjective and prone to bias, receipts provide objective proof that a task was performed by an agent or tool. This distinction is crucial for trust and accountability in decentralized AI networks where agents interact autonomously.

## How Wellknown Sees Signed Task Receipts
Wellknown indexes AI agents, MCP servers, and tools, distinguishing declared metadata from observed status. While receipts themselves are not indexed as standalone records, they relate closely to claimed records and agent identities. Wellknown’s infrastructure supports verifying claims and signatures attached to these receipts, ensuring that keys used for signing are linked to verified owners of records. This linkage is essential for validating the authenticity of receipts.

## Anatomy of a Signed Task Receipt
A signed task receipt typically includes:

- **Receipt Body:** The canonical data structure representing the task outcome or interaction details.
- **Canonical Hashing:** A deterministic hashing process applied to the receipt body to produce a unique digest.
- **Ed25519 Signatures:** Cryptographic signatures using Ed25519 keys that sign the canonical hash, providing non-repudiable proof of origin.

The cryptographic signature ensures that the receipt cannot be forged or altered without detection. Keys used for signing are attached to claimed records, which are verified through claim proofs such as DNS TXT records, wellknown-verify files at the domain root, or repository root files.

## Step-by-Step: Verifying Signed Task Receipts with Wellknown
1. **Claim Verification:** Confirm the ownership of the agent or server record by checking claim proofs. These include:
   - DNS TXT record at `_wellknown.YOUR-DOMAIN`
   - `https://YOUR-DOMAIN/.well-known/wellknown-verify.txt`
   - `.wellknown-verify` file at the repository root

2. **Retrieve Agent or Server Metadata:** Use the Wellknown HTTP API endpoint `https://wellknown.network/api/v1/agents/{id}` to fetch declared metadata about the agent or server associated with the receipt.

3. **Check Agent Status:** Query `https://wellknown.network/api/v1/agents/{id}/status` to observe the current operational status (live, recently observed, unavailable, unknown) of the agent or server.

4. **Validate Signature:** Using the Ed25519 public key attached to the claimed record, verify the signature on the canonical hash of the receipt body.

5. **Cross-Reference with Wellknown Index:** Optionally, use `https://wellknown.network/api/v1/search` or the MCP server tool `search_agents` to find related agents or tools and confirm consistency.

## What Changes Once Signed Task Receipts Are Used
The adoption of signed task receipts shifts the focus from subjective ratings to objective evidence. This enables:

- **Improved Trust:** Agents and users can verify task completion cryptographically.
- **Accountability:** Signed receipts provide audit trails linking actions to verified identities.
- **Interoperability:** Standardized receipt formats and signatures facilitate cross-agent communication and validation.

This approach complements existing agent discovery and status monitoring mechanisms indexed by Wellknown, enhancing the reliability of AI ecosystems.

## Common Mistakes and How to Avoid Them
- **Confusing Receipts with Ratings:** Receipts are evidence, not qualitative assessments. Avoid interpreting them as subjective scores.
- **Ignoring Claim Verification:** Without verifying claim proofs, signatures cannot be trusted. Always check claim tokens within their 7-day validity.
- **Using Non-Canonical Hashing:** Ensure the receipt body is hashed canonically before signing or verification to prevent mismatches.
- **Mismanaging Keys:** Keys must be properly attached to claimed records; otherwise, signature validation fails.
- **Overlooking Rate Limits:** When submitting or querying receipts via Wellknown’s API, respect the anonymous rate limit of 30 requests per minute and keyed limit of 120 per minute to avoid throttling.

## Additional Resources
For detailed technical specifications and examples, consult Wellknown’s documentation at:
- https://wellknown.network/docs/receipts
- https://wellknown.network/docs/claim
- https://wellknown.network/docs/status

This guide reflects data and standards as of 2026-11-18T00:29:49.303Z.
