1. The operator sets the purpose
Choose a disposable identity for a legitimate task and manage its records in the console. Registration on a target website is a separate step.
The workflow
From first login
to last request.
The operator manages an identity. An authorized client requests what it needs. The browser uses it on the intended site. Those are separate responsibilities.
Try the lifecycle.
Illustrative demo only.
No accounts created. No API requests.
POST
/v1/identitiesIdentity created
A dedicated identity for a research task.
- Identity
- research-001
- Identity status
- Active
- Data
- Example only
Creation does not register an account on another website.
Who does what
A broker.
Not a browser.
2. The client requests access
An authorized client requests the relevant credential or short-lived mail secret. Keep service credentials out of public pages, agent prompts and browser profiles.
3. The browser uses it carefully
The client must check the destination and origin before filling credentials or opening a verification link. Direct borz secret-filling integration remains planned.
4. The operator retires the identity
Revocation blocks future broker reads. Separately delete target-site accounts or rotate their passwords when needed: the broker cannot undo a password already returned.
Alongside the identity
Research has
its own record.
Signalport supports the discovery side of a task: find sources, keep reproducible queries and review the evidence. It does not need access to Aliasport’s credential store.
Explore source intelligence