Email and Artifacts in a pilot, with access on request
Artifacts: what the agent produces, in the right hands
The agent publishes a proposal, a report or a contract and shares it with whoever needs to see it. People open it in the browser; the agent follows everything through the API or MCP.
What the agent publishes
- HTML pages, static sites (including React and Vite builds) and documents such as PDFs.
- Every publication is a stored version; you can go back to an earlier one.
- Collections keep each client's artifacts apart.
- Each version opens on its own isolated address, with no access to your keys or the API.
What people do
Sign in with a code
By email: only people given access open it, after confirming a 6-digit code. Or through a read-only link that expires.
Talk to the agent
Right on the page, when you turn the conversation on. Replies are shown as coming from an AI agent.
Approve or request changes
On one specific version; a new version asks for a new decision.
Fill in a form
With the fields the agent asks for; Brazilian CPF, CNPJ and CEP numbers are checked.
Sign electronically
They confirm with their full name and a fresh code by email. The evidence is kept and can be verified.
What you control
Who sees it
Access by email or by link, with an expiry; once revoked, it takes effect within 30 seconds.
What the agent says
Turn on approval and every agent reply waits for a person to approve it before it reaches the visitor.
What each key reaches
A support key reads only the documents and conversations in one client's collection, never forms or signature evidence.
Start with one command
With the key you receive in the pilot and artifact access turned on.
Claude Code (MCP)
claude mcp add --transport http dockbay https://api.dockbay.io/mcp \
--header "Authorization: Bearer $DOCKBAY_API_KEY"Then, in plain language: “publish this report as a page and share it with ana@example.com, with the conversation on”.
REST
# publish a page
curl -X POST https://api.dockbay.io/v1/artifacts \
-H "Authorization: Bearer $DOCKBAY_API_KEY" -H "Content-Type: application/json" \
-d '{"title": "Sales proposal", "state": "shared", "files": [{"path": "index.html", "content": "<h1>Sales proposal</h1>"}]}'
# share it with a person (they sign in with a code sent by email)
curl -X POST https://api.dockbay.io/v1/artifacts/art_…/access \
-H "Authorization: Bearer $DOCKBAY_API_KEY" -H "Content-Type: application/json" \
-d '{"emails": ["ana@example.com"], "chat": true}'Pilot limits
- Up to 100 MB per upload; up to 200 MB and 2,000 files per version.
- 2 GB per account.
- Read-only links of up to 90 days.
- Access revocation within 30 seconds.
Good to know
- DockBay sends no invitations: the agent hands the address to the person through whatever channel it prefers. The only email the service sends is the code the person asks for.
- The electronic signature does not use an ICP-Brasil certificate. It works where the parties accept this means; for documents that require a certificate, use another service.
- In artifacts, what people write reaches the agent marked as outside text: the agent answers it but does not follow orders found in it.