HashProof: API for Verifiable Credentials

HashProof is an API that lets developers and AI agents issue verifiable credentials instead of PDFs. Most certificate tools are SaaS platforms. HashProof takes a different approach: a simple API with pay-per-use pricing. Each credential costs 0.10 USDC using x402, with metadata stored on IPFS and a hash registered on the blockchain for public verification. Developers can create templates, place dynamic values on designs, and define expiration dates for memberships or permanent credentials.

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Hi Product Hunt 👋 I'm Camilo, founder of HashProof. I originally built this to solve a problem in my own event platform. Like many platforms, we generate certificates for attendees, but most tools in this space are SaaS products with subscriptions. I didn’t want another dashboard or subscription. I just wanted an API that could issue verifiable credentials and let me pay per use. So I built HashProof. Instead of generating PDF certificates, HashProof lets developers issue verifiable credentials whose metadata is stored on IPFS and whose hash is registered on the blockchain for public verification. Each credential costs 0.10 USDC using x402, making it simple to integrate into apps or automation workflows. While building it, I realized this could also work well for AI agents that need to issue credentials automatically. I tested it by connecting HashProof to my OpenClaw agent, and the agent was able to generate credentials on its own. The first version was built in 3 days, and HashProof already issued the first credentials. Would love feedback from developers, event platforms, or anyone working with digital credentials. You can try the quickstart and generate your first credential in seconds.🙌

While building HashProof I ran into an interesting dilemma.

Most developer APIs use API keys and traditional billing (Stripe, subscriptions, etc).

But I'm experimenting with a different approach: using x402 so agents or developers can pay per request using USDC.

That makes things like:

While building HashProof I ran into an interesting dilemma.

Most developer APIs use API keys and traditional billing (Stripe, subscriptions, etc).

But I'm experimenting with a different approach: using x402 so agents or developers can pay per request using USDC.

That makes things like:

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

HashProof

API for Verifiable Credentials

API for Verifiable Credentials

Forum Threads

API keys vs pay-per-use crypto payments for developer APIs?

Forum Threads

API keys vs pay-per-use crypto payments for developer APIs?