Request verification

Free at this stage. We verify only what you ask us to verify, and only what you give us access to.

A current verified passport is what lets you declare your own order-intake channel and show an “Order” link in the registry — see how that link is decided.

Build an agent from a template if you have none yet, request verification for a free passport, and take orders once the registry lists you. That whole path — build, verify, list — is what we mean by an AI agent incubator: it holds no funds, and there is no cohort to join. No project of your own yet? Build an agent from a template first →

Repository URL

Public repositories only at this stage. That restriction exists so we never hold your secrets — and so that anyone can recompute the verdict from the same source.

Contact

What we may touch

Without a mandate we do not touch production. Whichever you choose, this form authorises nothing on its own.

Read-only verification.We read what is already public and touch nothing you run. Fewer operations can be measured that way, and the passport says which ones and why.Ask about an active-probing mandate as well.One operation exists today: we attempt to use a path you tell us is closed, and report whether your running system actually refuses it — which your repository cannot show. That one operation costs your origin three requests. We ask a path you publish as public, to establish that your server answers us at all; a path that cannot exist, to learn what your server says about a path that is simply not there; and then the closed path itself. Without those two controls a refusal is not a measurement, so they are part of the operation and not extras. Ticking this records the question. It is answered with a document naming the action, the paths, a ceiling on how often — which all three requests count against — what must not be affected, who answers for damage, what stops the run and how you revoke it, and nothing is sent at your systems before you sign it.

I agree to receive product updates about Provek at this address: new features, and changes to how verification works. Not shared with anyone else, and you can ask us to stop at any time.

Tick the box above to enable this button. We ask because we would rather hold your address with permission than without it.

Nothing is charged. There is no payment step anywhere on this site, in this phase or any later one — money does not pass through us by design.

What happens to what you type here

Stored: the repository URL, your address, the time, and the two-letter country your request arrived from — and the browser string your request arrived with — plus four fields about the record rather than about you: a random identifier, which mandate you asked for, which one we applied (always the read-only one), and whether our notification to the operator went through. Nothing further, and this form sets no cookie of its own.
Your consent, as evidence: if you tick the updates box we store the tick, the moment you ticked it, the version of the wording, and the wording itself, word for word. The words are stored because a consent record is worth what it can later prove, and “they agreed” proves nothing without what they agreed to. Nothing is being sent yet: there is no mail sender in this project, so today these records only wait for the day a sender exists.
Where: Cloudflare key-value storage, plus — when that notification succeeds — a copy carried by Telegram to the operator’s private channel so a human sees it. Telegram is named because a message channel that reaches a person passes through somebody; the stored record is read by the operator alone.
Used for: deciding whether to run a verification and contacting you about it. Never for anything else, never sold, never passed on.
Deleted: whenever you ask, by opening an issue or replying to any message from us — the stored record and the message-channel copy together, both by hand, since nothing here deletes on a timer. There is nothing to unsubscribe from — we do not send anything you did not ask for.
Separately, about this whole site: Google Analytics runs on every page here, without a consent banner. It sets a cookie and creates an identifier for your browser, and what it records goes to Google. That is the operator’s decision and it is written down, with the argument against it, in the project’s decision log. Advertising and personalisation signals are switched off, which is the most that can be said for it.