Getting access

Vectadyne is in private beta. There is no self-serve signup yet, and no public GA date — when one exists it will be stated here rather than implied.

What you need

Two values, and nothing else:

VECTADYNE_MCP_URL	the MCP endpoint — https://api.vectadyne.ai/mcp unless you were given another
VECTADYNE_TOKEN	a bearer token for a principal in your tenant

export VECTADYNE_MCP_URL="https://api.vectadyne.ai/mcp"
export VECTADYNE_TOKEN="…"     # keep this out of your shell history

https://api.vectadyne.ai is the canonical origin: the REST API lives at /v1 on the same host, and it is the OAuth issuer every discovery document is built from.

Code samples on this site read both values from the environment rather than hardcoding them. That is deliberate — a sample you copy should keep working against a different tenant, a future staging environment, or your own deployment. No page prints a credential, or a loopback address: the local simulator is for design partners with repository access, and a sample carrying its address would be telling you to connect to your own machine.

Before a token arrives

One call works without authentication, and it is the first step of the quickstart for that reason:

curl -s "$VECTADYNE_MCP_URL" \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"server/discover"}'

server/discover proves the endpoint is reachable and tells you which protocol version and verbs it serves. If that works and everything else returns unauthenticated, your networking is fine and you are waiting on a credential — which is a much better place to be than not knowing which of the two is wrong.

Tokens for people, credentials for machines

A bearer token identifies a principal. For a human at a terminal that is you. For anything that runs unattended — CI, a scheduled agent, a fleet member — you want a machine principal with its own credential, its own scope, and its own audit trail, rather than a person’s token in a secret store.

See Enrol a machine principal. Do this before you put anything in CI; retrofitting identity onto an audit log that already blames a human is not fun.

Joining the beta

Request access from vectadyne.ai. Design partners get repository access as well, which unlocks running locally.