Guides

Embed script

A single script tag puts Verivyx in front of your pages. It runs the human check and the bot gate client-side, then talks to the Verivyx API to deliver or withhold content.

On WordPress? You don't need this tag — install the Verivyx plugin, activate it, and the gate is added for you (no code).

The tag

html
<script
  src="https://api.verivyx.com/gate.min.js"
  data-domain="your-domain.com"
  data-api="https://api.verivyx.com"
  async
></script>

Attributes

  • src — the Verivyx gate script. Always loaded from api.verivyx.com/gate.min.js.
  • data-domain — the domain you registered in Verivyx. Must match exactly; this is how Verivyx looks up your pricing and wallet.
  • data-api — the Verivyx API base URL (https://api.verivyx.com).
  • async — load without blocking your page render.

Placement

  • Add the tag once per domain, not once per page — it applies to your whole property.
  • Place it just before the closing </body> tag.
  • Get the exact, pre-filled snippet from Set up integration.

Required content container

The gate hydrates the real article into an element with the id vx-article. Wrap the content you want to protect in that container — if no element with id="vx-article" exists, the hydrate script silently no-ops and verified humans never see the body.

html
<article id="vx-article">
  <!-- your article body -->
</article>
Only one #vx-article element is needed, on the pages you protect. The server fills it in for verified humans; for agents it stays withheld and the origin returns 402.

What it does

  • Runs a silent proof-of-work and fingerprint check to distinguish humans from agents — no captcha for real users.
  • For verified humans, content is hydrated normally.
  • For unverified/agent traffic, the origin responds with 402 Payment Required and x402 payment requirements instead of your content.
The script is a gate, not the security boundary. The real protection is the server-side hydration check plus on-chain payment verification — never put secrets or access logic in the client.

Curious what happens on the agent side of that 402? See How agents pay (x402).