ARCY AI

Origins

Add the domains your Product runs on, prove you control each one with a DNS record, and choose which environments may serve sessions from it.

Autopilot > Origins is where you add the domains your Product runs on and prove you control them. ARCY refuses sessions from a domain until it is verified here and assigned to an environment.

Before you start

  • Only an admin can add, verify, edit, assign or remove an origin. Members see the list.
  • Your Plan sets how many origins you can hold, pending and verified together. See Billing. At the cap, Add origin is disabled until you remove one.
  • You need access to the DNS records of the domain.

Setting it up

  1. Choose Add origin and enter the full address with its scheme, for example https://myapp.com.
  2. The new row shows Pending and the DNS TXT record to publish: type TXT, a name of _arcy-verify. followed by the hostname, and a generated value. Add it with your DNS provider.
  3. Once the record has spread, choose Verify. The row changes to Verified.
  4. Open the environments menu on the row and tick every environment that may serve sessions from this origin. Each change saves as you make it.

Which hostnames one proof covers, where the check runs, and how localhost is treated are on Session security.

What it changes

  • A Pending origin is trusted for nothing. A page on it cannot start ARCY.
  • A Verified origin assigned to no environment is refused too, and the row says so. Assign at least one environment.
  • Editing the address keeps the environments you assigned. If the domain itself changes, the row goes back to Pending and you publish a new record for the new domain.
  • Removing a pending origin happens at once. Removing a verified one asks you to type the domain first.

Removing a verified origin cannot be undone. Every page on that domain stops starting ARCY until you add and verify it again.

When it goes wrong

Verify fails. The name or the value does not match, or the record has not spread yet. Compare both against the row character by character, wait for your DNS provider's propagation time, then choose Verify again.

Sessions are refused after verifying. Open the environments menu on the row. A verified origin serves only the environments ticked there, and the environment whose Token your snippet carries must be one of them.

See also

On this page