{"id":38025,"date":"2026-10-02T08:05:03","date_gmt":"2026-10-02T08:05:03","guid":{"rendered":"https:\/\/thebluemanakin.com\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/"},"modified":"2026-10-02T08:05:03","modified_gmt":"2026-10-02T08:05:03","slug":"zkapi-vs-export-controls-the-collision-nobody-admits","status":"publish","type":"post","link":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/","title":{"rendered":"zkAPI vs. export controls: the collision nobody admits"},"content":{"rendered":"

On 1 October 2026 the Ethereum Foundation shipped zkAPI<\/a> to mainnet, a system that lets users pay for calls to metered APIs \u2014 AI models among them \u2014 without the provider or the payment server being able to link a request to a payer. The user deposits ETH or USDC into a vault contract that records their balance as a private note; to spend, their own machine generates a zero-knowledge proof showing the request is backed by funds, without revealing which note or which deposit it came from. The server validates the proof and issues a temporary API key with a spending cap. Every payment publishes a nullifier<\/em>, a serial number that prevents the same balance being spent twice and, according to the Foundation, exposes nothing else.<\/p>\n

The client exposes the standard OpenAI and Ollama APIs on localhost. Which means any existing editor, chat client or agent works simply by pointing it at your machine. There is no integration friction. The design implements “ZK API Usage Credits”<\/strong>, the proposal that Davide Crapis \u2014 head of the Foundation’s dAI team \u2014 and Vitalik Buterin published on the Ethereum Research forum on 11 February. The same team shipped ERC-8004, the identity standard for agents, to mainnet in January.<\/p>\n

Coverage has read this as a privacy launch. It is one. But it is also, and above all, infrastructure that dismantles the only effective control point that currently exists over who gets access to frontier models.<\/p>\n

AI enforcement isn’t the chips: it’s the API key<\/h2>\n

For three years the public debate about AI export control has revolved around hardware: H100s, licences, GPU smuggling routes. But access to frontier capability no longer requires owning the silicon. It requires an account. And the identity chain that underpins that account is precisely the one the Foundation itself describes in its announcement: “your API key points to an account, the account to a payment method, and every prompt you send adds to the record tied to both”<\/em>.<\/p>\n

That sentence, written as an indictment of commercial surveillance, is also a precise description of the compliance mechanism. The inference provider knows who pays because there is a card behind it. It knows where the payment comes from because there is a BIN, an issuing country, a correspondent bank. Everything else is built on top of that knowledge: blocking of sanctioned jurisdictions, detection of abuse clusters, account suspension, and the theoretical ability to certify to a regulator that no listed entity has consumed frontier compute.<\/p>\n

Anyone who wants proof that this control is both real and porous should read The Economist<\/a>‘s reporting on the use of crypto cards to pay for US models from jurisdictions those models should never reach. The pattern matters more than the volume: the leak doesn’t go through the technical perimeter, it goes through the payment layer. A prepaid card issued against a stablecoin balance, with weak or recycled KYC, turns a geographic block into a formality.<\/p>\n

Why distillation turns this into a national security problem<\/h2>\n

The second axis explains why Washington cares. On 1 July, according to OpenAI, an extraction campaign began that by 24 and 25 July had reached 16,000 requests from more than 4,000 users<\/strong>, within a cluster of over 15,000 accounts. OpenAI says it neutralised the campaign on 28 July and attributes a core of the activity to people linked to Moonshot AI<\/a>, the company behind Kimi, while admitting it does not know whether all the operators answer to a single actor.<\/p>\n

The target was not the answers but the hidden reasoning: the encrypted scratchpad<\/em> the model generates before responding. One of the techniques involved lifting the encrypted reasoning out of one conversation and asking the model to decrypt it in another. There was no break in the encryption and no access to databases; there was manipulation of interactions at scale. OpenAI calls it adversarial distillation, and the track record is long: DeepSeek in January 2025, the 24,000 fraudulent profiles and more than 16 million exchanges with Claude<\/strong> that Anthropic reported in February, Anthropic’s June request to Congress to criminalise mass model extraction, and Elon Musk’s admission in court that xAI distilled OpenAI models to train Grok.<\/p>\n

Look at the defence mechanism in every one of those cases: identify accounts, correlate them, shut them down. Anti-distillation is, operationally, pattern detection over linkable identities. If you cannot group 4,000 users into a cluster because there is nothing to group them by \u2014 no common payer, no card, no billing history \u2014 the only trace left is the content of the prompts and the IP. And zkAPI’s own documentation acknowledges both as open limitations: the gateway can correlate requests from a stable IP, and sessions can be re-linked through content, writing style or conversation history. The Foundation’s recommendation for anyone who wants strong privacy is to route over Tor.<\/p>\n

Incompatible by design<\/h2>\n

Here is the collision. An inference provider subject to OFAC sanctions and to model diffusion rules needs to be able to assert two things: that no listed entity is among its customers, and that it can identify and cut off coordinated abuse. An unlinkable payment system makes the first assertion impossible and reduces the second to weak, rebuttable signals.<\/p>\n

This is not a problem of intent. It is a problem of architecture. The two designs optimise opposite variables over the same piece of data: either the provider knows who paid, or it cannot comply<\/strong>. Zero-knowledge cryptography does not soften that tension, it makes it mathematically unavoidable. And the industry is building both at once without acknowledging the contradiction: the same ecosystem funding agent identity standards (ERC-8004) and machine-to-machine payments is publishing the instrument that turns inference consumption into spending with no identifiable payer.<\/p>\n

The operational question is not philosophical. It is: who carries the risk? If a zkAPI relay issues temporary API keys against proofs, is it a payment services provider? A neutral technical intermediary? A money transmitter? If a sanctioned entity consumes frontier compute through an anonymous vault, liability falls on the lab that served the inference, on the operator of the zkAPI server, or on nobody. In Europe, MiCA and the crypto-asset transfer framework have moved in the opposite direction to unlinkable payments; in the United States, the Tornado Cash precedent suggests that the technical neutrality of software is not always a sufficient defence for its operators.<\/p>\n

What could prove this reading wrong<\/h2>\n

There are several reasons to think this collision will never materialise, and they deserve to be taken seriously.<\/p>\n

    \n
  • The repository describes the protocol as experimental.<\/strong> That is not a disclaimer to be waved away: a system that requires depositing into a vault, managing private notes and generating proofs locally has an adoption curve that will keep it marginal for quite some time. Client-side friction is low; custody friction is not.<\/li>\n
  • Payment unlinkability is not anonymity.<\/strong> If the gateway correlates by IP and content re-links sessions, a state actor with traffic analysis and stylometry capabilities can reconstruct clusters without touching the payment layer. The campaign OpenAI attributes to people linked to Moonshot was detected by request pattern, not by the card.<\/li>\n
  • The cheapest route around controls is still the most boring one.<\/strong> Intermediaries with lax KYC, purchased accounts, corporate proxies in third countries. Nobody needs zero-knowledge proofs to do what is already being done with a prepaid card, as The Economist describes.<\/li>\n
  • An intermediate design could emerge.<\/strong> Proofs of non-membership in sanctions lists, jurisdiction attestations without identity disclosure, verifiable credentials with revocation. None of that exists in production for inference today, but it is technically coherent and would be the natural way out if regulators apply pressure.<\/li>\n<\/ul>\n

    If any of those four hold, zkAPI ends up as an interesting piece of R&D with no regulatory impact. My reading is that this delays the collision rather than avoiding it: the vector labs worry about today \u2014 industrial-scale distillation \u2014 gets cheaper precisely as payment stops being a signal. And the use case the Foundation itself lists first, autonomous agents paying for inference, is exactly the one that scales without human supervision.<\/p>\n

    What this changes if you build or invest<\/h2>\n

    For anyone building payment infrastructure on top of AI consumption, the design decision is no longer just about product: payer linkability is a compliance parameter, and it should be treated as one from day one. A system that cannot answer “who paid for this request” cannot answer a legal demand either, and the cost of retrofitting that capability onto a private-note architecture is close to redesigning it.<\/p>\n

    For investors, the opportunity does not lie in pure anonymity \u2014 which hits a regulatory ceiling in any jurisdiction with crypto-asset transfer rules \u2014 but in the layer that does not yet exist: proofs of eligibility without identity<\/strong>. Demonstrating cryptographically that a payer is not on a sanctions list, that they operate from a permitted jurisdiction, or that they do not exceed an aggregate consumption threshold, without revealing who they are. That is an open problem and the only point where the two architectures can coexist.<\/p>\n

    And for the labs: if customer identity stops being a reliable signal, distillation detection will have to lean on behaviour \u2014 query signatures, reasoning-extraction patterns, watermarking of outputs. Which means more telemetry on prompts, not less. The paradoxical outcome of a private payment system may be a content inspection regime more intrusive than today’s.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The Ethereum Foundation has shipped a mainnet system that lets you pay for AI inference without the provider being able to link the request to whoever paid for it. That is the exact opposite of the compliance architecture Washington is building on top of access to frontier models.<\/p>\n","protected":false},"author":6,"featured_media":38026,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","telegram_tosend":false,"telegram_tosend_message":"","telegram_tosend_target":0,"footnotes":""},"categories":[369],"tags":[2645,2705,2699,2703,2704,1136,2698],"class_list":["post-38025","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-our-blog-en","tag-compliance","tag-crypto-payments","tag-ethereum-foundation","tag-export-control","tag-model-distillation","tag-privacy","tag-zkapi"],"yoast_head":"\nzkAPI vs. export controls: the collision nobody admits | Blue Manakin<\/title>\n<meta name=\"description\" content=\"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"zkAPI vs. export controls: the collision nobody admits | Blue Manakin\" \/>\n<meta property=\"og:description\" content=\"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/\" \/>\n<meta property=\"og:site_name\" content=\"Blue Manakin\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-02T08:05:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Luca Zollino\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@thebluemanakin\" \/>\n<meta name=\"twitter:site\" content=\"@thebluemanakin\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Luca Zollino\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/\"},\"author\":{\"name\":\"Luca Zollino\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#\\\/schema\\\/person\\\/37e758cc1705602d77339cffc99731de\"},\"headline\":\"zkAPI vs. export controls: the collision nobody admits\",\"datePublished\":\"2026-10-02T08:05:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/\"},\"wordCount\":1552,\"publisher\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/either-the-provider-knows-who-paid-or-it-cannot-comply.png\",\"keywords\":[\"compliance\",\"crypto payments\",\"ethereum foundation\",\"export control\",\"model distillation\",\"privacy\",\"zkapi\"],\"articleSection\":[\"Our Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/\",\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/\",\"name\":\"zkAPI vs. export controls: the collision nobody admits | Blue Manakin\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/either-the-provider-knows-who-paid-or-it-cannot-comply.png\",\"datePublished\":\"2026-10-02T08:05:03+00:00\",\"description\":\"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/either-the-provider-knows-who-paid-or-it-cannot-comply.png\",\"contentUrl\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/either-the-provider-knows-who-paid-or-it-cannot-comply.png\",\"width\":1200,\"height\":630,\"caption\":\"Either the provider knows who paid, or it cannot comply\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/zkapi-vs-export-controls-the-collision-nobody-admits\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thebluemanakin.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Our Blog\",\"item\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/category\\\/our-blog-en\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"zkAPI vs. export controls: the collision nobody admits\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#website\",\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/\",\"name\":\"Blue Manakin\",\"description\":\"Blue Manakin. Come Dance With Us!\",\"publisher\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thebluemanakin.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#organization\",\"name\":\"Blue Manakin\",\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2021\\\/07\\\/cropped-logo-header.png\",\"contentUrl\":\"https:\\\/\\\/thebluemanakin.com\\\/wp-content\\\/uploads\\\/2021\\\/07\\\/cropped-logo-header.png\",\"width\":613,\"height\":250,\"caption\":\"Blue Manakin\"},\"image\":{\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/thebluemanakin\",\"https:\\\/\\\/www.instagram.com\\\/thebluemanakin\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/blue-manakin\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thebluemanakin.com\\\/#\\\/schema\\\/person\\\/37e758cc1705602d77339cffc99731de\",\"name\":\"Luca Zollino\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g\",\"caption\":\"Luca Zollino\"},\"url\":\"https:\\\/\\\/thebluemanakin.com\\\/en\\\/blog\\\/author\\\/luca-zollino\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"zkAPI vs. export controls: the collision nobody admits | Blue Manakin","description":"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/","og_locale":"en_US","og_type":"article","og_title":"zkAPI vs. export controls: the collision nobody admits | Blue Manakin","og_description":"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.","og_url":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/","og_site_name":"Blue Manakin","article_published_time":"2026-10-02T08:05:03+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png","type":"image\/png"}],"author":"Luca Zollino","twitter_card":"summary_large_image","twitter_creator":"@thebluemanakin","twitter_site":"@thebluemanakin","twitter_misc":{"Written by":"Luca Zollino","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#article","isPartOf":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/"},"author":{"name":"Luca Zollino","@id":"https:\/\/thebluemanakin.com\/#\/schema\/person\/37e758cc1705602d77339cffc99731de"},"headline":"zkAPI vs. export controls: the collision nobody admits","datePublished":"2026-10-02T08:05:03+00:00","mainEntityOfPage":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/"},"wordCount":1552,"publisher":{"@id":"https:\/\/thebluemanakin.com\/#organization"},"image":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#primaryimage"},"thumbnailUrl":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png","keywords":["compliance","crypto payments","ethereum foundation","export control","model distillation","privacy","zkapi"],"articleSection":["Our Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/","url":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/","name":"zkAPI vs. export controls: the collision nobody admits | Blue Manakin","isPartOf":{"@id":"https:\/\/thebluemanakin.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#primaryimage"},"image":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#primaryimage"},"thumbnailUrl":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png","datePublished":"2026-10-02T08:05:03+00:00","description":"The Ethereum Foundation's zkAPI lets users pay for AI models with no linkable identity. It collides head-on with the KYC that underpins AI export control.","breadcrumb":{"@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#primaryimage","url":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png","contentUrl":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2026\/10\/either-the-provider-knows-who-paid-or-it-cannot-comply.png","width":1200,"height":630,"caption":"Either the provider knows who paid, or it cannot comply"},{"@type":"BreadcrumbList","@id":"https:\/\/thebluemanakin.com\/en\/blog\/zkapi-vs-export-controls-the-collision-nobody-admits\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thebluemanakin.com\/"},{"@type":"ListItem","position":2,"name":"Our Blog","item":"https:\/\/thebluemanakin.com\/en\/blog\/category\/our-blog-en\/"},{"@type":"ListItem","position":3,"name":"zkAPI vs. export controls: the collision nobody admits"}]},{"@type":"WebSite","@id":"https:\/\/thebluemanakin.com\/#website","url":"https:\/\/thebluemanakin.com\/","name":"Blue Manakin","description":"Blue Manakin. Come Dance With Us!","publisher":{"@id":"https:\/\/thebluemanakin.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thebluemanakin.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/thebluemanakin.com\/#organization","name":"Blue Manakin","url":"https:\/\/thebluemanakin.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/thebluemanakin.com\/#\/schema\/logo\/image\/","url":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2021\/07\/cropped-logo-header.png","contentUrl":"https:\/\/thebluemanakin.com\/wp-content\/uploads\/2021\/07\/cropped-logo-header.png","width":613,"height":250,"caption":"Blue Manakin"},"image":{"@id":"https:\/\/thebluemanakin.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/thebluemanakin","https:\/\/www.instagram.com\/thebluemanakin\/","https:\/\/www.linkedin.com\/company\/blue-manakin"]},{"@type":"Person","@id":"https:\/\/thebluemanakin.com\/#\/schema\/person\/37e758cc1705602d77339cffc99731de","name":"Luca Zollino","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/656a41dac68f7e776f7e8c5bf69fe105291797157b051b7d978ca0cae869da58?s=96&d=mm&r=g","caption":"Luca Zollino"},"url":"https:\/\/thebluemanakin.com\/en\/blog\/author\/luca-zollino\/"}]}},"_links":{"self":[{"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/posts\/38025","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/comments?post=38025"}],"version-history":[{"count":0,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/posts\/38025\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/media\/38026"}],"wp:attachment":[{"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/media?parent=38025"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/categories?post=38025"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thebluemanakin.com\/en\/wp-json\/wp\/v2\/tags?post=38025"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}