For AI service providers · Capability
What can a client portal for AI services do?
The Agentic Workers customer portal lets a client send files to a selected Super Agent or authorize supported tools through a scoped link without an Agentic Workers account. It is an intake surface. It is not a complete client dashboard, billing portal or automatic review-and-delivery system.
By Agentic Workers Team · Published · Updated
Send a link for the right job
Create an upload link or an app-connection invitation for the selected agent. Choose a label and expiry. The client follows the link and completes the requested step. Use a separate link when the agent or task boundary changes.
Confirm receipt before using the input
Check the upload receipt and saved file before running the workflow. Upload completion does not automatically start an agent turn. The connected computer must be available for supported file transfers; older runtimes can require an update before link creation.
Close access deliberately
Revoking a link blocks new portal requests. It does not delete files already received or disconnect accounts already authorized. For app offboarding, revoke active invitations and disconnect the app account separately.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Invite
Provider creates a link for one selected agent and a defined expiry.
- 02
Submit
Client uploads a file or completes the supported app authorization.
- 03
Confirm
Provider checks the receipt or active account and starts the agreed work.
Fit and limitations
- Good fit
- Providers who need scoped file intake and client tool authorization.
- Poor fit
- A branded client login with project status, invoices and granular client roles.
- Known limits
- A link can be used by anyone who possesses it until it expires or is revoked. Share it through an agreed channel. Uploads do not imply approval to publish the files.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Customer portal operating notesProduct documentation | Upload and app-connection invitations are scoped to a selected agent. Revoking an invitation is separate from disconnecting an account. | |
| Customer portal production releaseProduct documentation | Agent-created customer upload links shipped on October 16, 2026. Link creation and file receipt do not automatically start an agent turn. | |
| Connect tools to a Super AgentProduct documentation | Authorization requirements depend on the provider. Verify the actual account and resource access with a read-only request. |
Questions providers ask
What should we test before using client data?
Provider creates a link for one selected agent and a defined expiry. Client uploads a file or completes the supported app authorization.
What should the provider verify after a run?
Provider checks the receipt or active account and starts the agreed work.
What is the main limitation?
A link can be used by anyone who possesses it until it expires or is revoked. Share it through an agreed channel. Uploads do not imply approval to publish the files.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now