Control access and manage your data

Check who can reach your workspace, what AgentLinkOps keeps and how to take it with you or delete it. The privacy policy covers the legal terms.

​

Use AgentLinkOps without an account

The free backlink checker and the local CLI check need no account. The free checker reads one linking page per check, allows three checks per visitor per UTC day and reuses a result for 15 minutes. It never returns the publisher’s HTML. Hosted monitoring needs a workspace.

​

Control who can see your workspace

Every person joins a workspace as an owner, admin, member or viewer. Owners, admins and members can change records. Viewers can read records and manage their own notification settings within the websites they can access.

• Invite someone by email and choose their role. You can limit them to named websites. An invitation can’t grant a role or a website you don’t hold yourself.
• Invitation links only work for the invited email. The person must sign in with that verified address, so a forwarded link can’t admit someone else. AgentLinkOps stores a hash of the invitation token, not the token.
• Removing someone works at once. Membership is checked on every request, including requests from their agents and API keys.

​

Limit what agents and API keys can do

An agent reaches your workspace through MCP with browser approval, through the HTTP API with a scoped API key, or through the CLI with either. Each request is checked against the credential’s scopes and the member’s current access.

• Agent approval is per client and per workspace. The approval screen names the scopes requested, and approving never grants more than the approving member holds. You can revoke an approved agent in the workspace.
• An API key carries only scopes its owner holds. When an owner’s role or website access narrows, their existing keys narrow with it. A key limited to certain websites can’t create new ones.
• Keep credentials out of chats. Don’t paste API keys, tokens or one-time codes into a conversation with an agent. Approve access on the AgentLinkOps screen and store keys in your client’s secret storage.

What each scope permits

Scope	Permits
projects:read	Read workspace limits, usage, websites and members
projects:write	Create websites, invite members, change access and delete unused resources
watches:read	Read links, history, evidence snapshots, published and saved contacts, destination health and reports
watches:write	Add, update and pause links and destinations, request checks, set link types and tags, and save or delete contacts
events:read	Read the change feeds
notifications:write	Manage email notification settings within your website access
exports:create	Export links, link records, workspace data and CSV history
discovery:read	Read backlink searches, imports, candidates and competitor inventories
discovery:write	Run Find my backlinks and competitor lookups, import backlinks and search connection rows, verify candidates and manage competitor sets
classification:write	Save tags and display settings, tag links and correct link types. The app uses this scope; agent catalogs don’t list these commands

Owners, admins and members hold every scope. Viewers hold the read scopes and notifications:write. Connect an MCP client, connect the CLI or use the HTTP API to set up a credential.

​

What AgentLinkOps stores

• What you add: the linking pages and destinations you monitor, expected anchor text and link attributes, website and competitor domains, and the rows you import.
• Check results: each check’s date, result and reason. When the page was read, the record also holds the final URL after redirects, the HTTP status, robots information, a SHA-256 hash of the bytes read, and every matching link with its anchor and attributes.
• Evidence snapshots: a private copy of what each check read, so you can see what the page said at the time.
• Saved contacts: a name or organization, an optional email address and contact page, and the links each contact belongs to. No phone numbers, message text or replies. Anyone who can read the website can read its contacts. Saving or deleting them needs write access.
• Your campaign records: prospects, outreach status and last-contact dates you save. Message bodies, mailbox history, sequences and suppression lists stay in your sending tools. AgentLinkOps never sends outreach or connects to a mailbox.
• Change feeds and usage: link and destination events, and the credits or checks your workspace has reserved and used.

Payment details go through the payment provider’s checkout and are not stored in AgentLinkOps. Google and Bing data is read only after you connect an account under Settings › Search connections. Text on a publisher’s page is stored as untrusted data. It is never treated as an instruction to AgentLinkOps or your agent. Published contacts are only addresses and contact pages the publisher placed on a page AgentLinkOps saved in full. Nothing is guessed, and deliverability is never checked.

​

How long records are kept

A new check can read the current page, but it can’t recreate an expired snapshot. Download snapshots you need to keep while they are available. Evidence states shows how.

​

Plan limits and credits

On the Monitor plan and its trial, work draws on 30,000 shared credits per billing period:

• When credits are used. A check uses its credit once it starts, even if it later fails. A lookup uses its credits when its request goes out, and an audit uses them before each page is fetched. Only work cancelled before it starts gets its credits back.
• Monitoring comes first. Checks, lookups and audits you start, and scheduled audits, can only use the credits left after the forecast for the rest of the period’s scheduled checks.
• At the limit. New work stops. There are no overage charges. Credits reset when the next period begins. When a plan or trial ends, no new checks run and your records stay readable and exportable.
• Cadence. You choose how often each link is checked, from once an hour to once every 30 days.

Index checks use your Search Console quota, not credits. A subscription that started before shared credits keeps its check allowance. Read the balance with get_usage and see what planned work can use with estimate_usage before you start it.

​

Export your data

In Settings › General › Export, choose Download .zip for your links, your pages and a full workspace file with saved contacts. The workspace file lists what each table includes and leaves out. Raw evidence snapshots are not in bulk exports. Download each one from its check while it is retained. Sync and export covers agent exports with export_link_watches, the HTTP workspace export and the optional local ledger.

​

Delete records or the workspace

Delete one unused resource. A link, destination or website that has never run a check can be removed. Call preview_resource_deletion to see what it touches and the confirmation it needs, then delete_resource. A resource with check history can’t be deleted this way. Pause the link or destination to stop future checks and keep its evidence. Delete a website’s saved contacts before deleting the website. Delete the workspace. An owner, or an admin with access to every website, can delete the whole workspace:

1. If your plan still renews, cancel it under Plan first.
2. Open Settings › General and choose Delete workspace.
3. Choose Download export (.json) if you want a copy. The dialog lists what is deleted and what is kept.
4. Type the workspace name and choose Delete workspace.

Deletion runs in the background and can’t be undone. It removes websites, links, prospects, saved contacts, check history, evidence, stored page copies, tags, disavow lists, imports, alerts, members, invitations, API keys and agent access. Billing records stay for tax and accounting. Copies already outside the service, such as delivered emails and backups, follow the privacy policy. Agents and API keys can’t request workspace deletion. Your sign-in account is separate. Delete it under Account › Manage account after the workspace is gone.

​

Security questions

Email support@agentlinkops.com with security questions or deletion requests. AgentLinkOps has no SOC 2 report or other third-party audit yet.

​

Next step

Connect your agent with only the access it needs.