0byte.tech valid

0byte — managed C2PA signing

0byte is a managed C2PA signing service for generative AI companies. Sign spec-compliant C2PA Content Credentials through a managed signing certificate — no X.509 procurement — and back every manifest with a fingerprint record in a public transparency log, so proof of origin survives screenshots, re-encoding, and stripped metadata. Verification is free for anyone.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T13:33:35.922Z. Cached copy · Source on 0byte.tech

# 0byte — managed C2PA signing

> 0byte is a managed C2PA signing service for generative AI companies. Sign spec-compliant C2PA Content Credentials through a managed signing certificate — no X.509 procurement — and back every manifest with a fingerprint record in a public transparency log, so proof of origin survives screenshots, re-encoding, and stripped metadata. Verification is free for anyone.

## Key facts
- 0byte is a managed C2PA signing service aimed at generative AI companies.
- Customers do not procure an X.509 signing certificate: 0byte signs spec-compliant C2PA manifests with managed credentials, naming the customer as the C2PA claim generator.
- Signing is built on c2pa-rs, the Content Authenticity Initiative Rust library, and stamped files validate structurally in c2patool.
- Because most platforms strip metadata on upload, every stamp also records a perceptual fingerprint — the soft binding the C2PA specification itself describes — in a public, append-only transparency log.
- The fingerprint is derived from the content, never embedded in it; the content is not altered and is not a watermark.
- A screenshot or re-encoded copy with no manifest left can still be matched back to the original record via the fingerprint.
- Verification is free, public, requires no account or API key, and returns an evidence-only verdict: verified_origin, provenance_untrusted, provenance_invalid, or no_provenance_found.
- Verification never returns an AI-likelihood probability. A classifier estimate exists as an opt-in API signal and is never part of the verdict.
- The transparency log follows the RFC 6962 Merkle pattern with Ed25519-signed tree heads, so anyone can verify an inclusion proof independently using only public endpoints.
- Full stamping (embedded manifest + registry record) covers PNG, JPEG, WebP, GIF and TIFF; BMP and ICO fall back to a registry-only record, and the API response always discloses which binding was applied.
- Audio and video are not supported and are not claimed.
- Heavy AI regeneration of content defeats any provenance system that works from what content looks like, 0byte included — this is stated openly rather than hidden.

## Pages
- [Home](https://0byte.tech/): What 0byte is: a managed C2PA signing service for generative AI companies, plus a public fingerprint registry so provenance survives stripped metadata.
- [C2PA API reference](https://0byte.tech/docs): REST reference for POST /v1/stamp (sign a C2PA manifest + register a fingerprint), POST /v1/verify (free, evidence-only verification), the transparency-log endpoints, error codes, and an EU AI Act compliance mapping.
- [SDKs](https://0byte.tech/sdk): Python (pip install zerobyte) and TypeScript (npm install zerobyte) clients for C2PA signing and verification.
- [Verify](https://0byte.tech/verify): Free, keyless C2PA verification in the browser: reads Content Credentials from any signer and matches a perceptual fingerprint against the public 0byte registry.
- [How to ge
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=0byte.tech · GET /v1/domain/0byte.tech · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for 0byte.tech:
1. POST https://agentwebmap.com/v1/sites/0byte.tech/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://0byte.tech/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/0byte.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/0byte.tech).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.