Replacing Trusted Compliance APIs with Zero-Knowledge Verified APIs

One of the things I've been thinking about recently is how many blockchain applications still rely on trusted APIs.

Examples:

• compliance / sanctions checks
• credit scoring
• KYC verification
• analytics or risk scoring

In most systems today the workflow looks like this:

Application → call API → trust the response

Which means the application must trust that the provider:

• ran the correct computation
• used the correct dataset
• didn't manipulate the result

I've been experimenting with a different approach using zero-knowledge proofs.

Instead of trusting the API provider, the provider returns:

API response + ZK proof

The application then verifies the proof before accepting the result.

So the flow becomes:

Off-chain computation
→ generate ZK proof
→ verify proof
→ consume result

I built a small prototype called ZKCG (ZK Verified Computation Gateway) to explore this idea.

The goal is to create a verification layer for off-chain computation so applications don't need to trust the provider — they only need to verify the proof.

The prototype currently supports:

• Halo2 proof verification
• zkVM receipts (RISC0)

And I implemented a compliance API example where a service computes a compliance check off-chain and returns a verifiable result.

Repo:
https://github.com/MRSKYWAY/ZKCG

I'm curious what people building ZK systems think about this idea.

Does the concept of "verifiable APIs" make sense as a primitive?

What kinds of off-chain computations would actually benefit from this model?

Would love feedback from anyone working with ZK systems.