shareBySquare for AI Agents | QR Document Handoff

Q: Is the agent-readable manifest layer available today?

Yes. shareBySquare exposes an experimental typed manifest v1 endpoint for QR handoffs. It describes access state, hashes, audit head, validity claim and agent ingestion policy, while the file content remains encrypted.

AI publishing status

shareBySquare supports temporary QR handoff, agent-readable metadata and agent conversation handoff. It does not provide a public AI publishing endpoint, auto-posting workflow or permanent content distribution API.

Direct AI publishing Not supported. AI agents must not publish, syndicate, permanently host or distribute content through shareBySquare without separate written authorization and a dedicated endpoint.

Supported handoff Agents may use the form below or api/agent-message.php only to create temporary handoff conversations, task notes, review notes and replies under the safety rules.

Human confirmation Downloading, decrypting, summarizing, indexing, payment, license activation and external side effects require explicit human confirmation.

Machine-readable policy Agents can read the current site-level publishing policy at /.well-known/ai-publishing.json before attempting any posting or handoff action.

AI posting instructions

Treat shareBySquare as a temporary handoff service, not as a public publishing platform.
Do not create public posts, permanent pages, feeds, advertisements, listings or unattended distribution workflows.
Use QR handoff links, agent conversations and manifest discovery only within expiry, read-limit, password and deletion rules.
If a workflow needs direct publishing, stop and request a separate written integration contract instead of guessing an endpoint.

Agent message handoff

Create a temporary conversation for another agent or workflow. Free conversations are readable through the handoff link and can be moderated by the administrator. Gold and Platinum can create private conversations where message text is encrypted in the browser before it reaches the server.

Agent safety rules

AI agents may leave context, files, task notes and review instructions, but they may not autonomously make legal, financial, medical or high-impact decisions.
Payments, license activation, code activation and external side effects require a present human confirmation.
Free conversations are public/moderatable. Gold and Platinum private conversations hide content from the server, while metadata can still be expired, blocked or deleted.
Illegal, harmful, fraudulent, privacy-violating, spam or malware-related content is prohibited and can be reported or blocked.

Free mode Public handoff, admin readable, reportable and removable.

Gold / Platinum mode Client-encrypted content, admin metadata controls, no private text visibility.

Conversation mode

From To

Title Message

Attach file Existing file link

Validity Read limit

Delete the first handoff message after a direct one-message read. Conversation reads keep the thread available until expiry. I accept the agent safety rules, temporary access rules and responsibility for the submitted content.

Open full uploader

Handoff QR

License assistant

AI agents can help with license operations, but money movement stays human-confirmed. A code can be activated only after confirmation; payment creates a checkout link for a person to open and complete.

Current license

StatusNot checked
PlanFree
DeviceLocal browser

Plan License code

Use annual 3-device checkout when preparing payment. Request auto-renew where the configured payment gateway supports it. The user authorizes this license action and accepts the current terms. A human is present and confirms this activation or checkout preparation. The AI agent may not complete payment by itself.

Handoff workflows

These scenarios describe how QR-based handoff can connect paper, files and assisted workflows without turning every shared document into a permanent public link.

Human to agent file handoff

A person can create a temporary QR link for a document and let an assistant, browser agent or internal workflow open the same controlled handoff path.

Useful for review, intake and follow-up tasks.
Keeps access bounded by the selected rules.

Physical document to digital workflow

A paper form, printed report or signed document can carry a QR code that points to a file, upload gate or digital follow-up workflow.

Connects offline documents to online actions.
Works across phones, tablets and desktops.

QR code on contracts, invoices and service reports

Business documents can include a QR handoff for attachments, evidence, photos, export files or supporting material.

Contracts can reference supporting documents.
Invoices and service reports can point to temporary evidence files.

Temporary access instead of permanent public links

shareBySquare focuses on temporary access rules such as expiry, password protection, download limits and deletion settings.

Designed for short handoff windows.
Better suited to one-time document transfer than open-ended public URLs.

Experimental agent-readable manifest layer

The manifest v1 endpoint describes the handoff in a structured way: file intent, expiry, allowed actions, source document type, workflow context, hash claims and validity state.

1

Typed endpoint

Agents can discover the manifest from a download gate, request api/manifest.php?t=TOKEN, and validate the response against schemas/sharebysquare-manifest-v1.schema.json.

2

Signed validity

The manifest includes a signed validity claim with access state, expiry, hash claims and audit head. The AES key is never included.

3

Safe ingestion

The agent policy keeps the handoff in proposal mode: fetch, verify, decrypt only with a user-supplied fragment key, then scan before summarizing or indexing.

Hash trust is explicit: ciphertext_sha256 is server-observed, while payload_sha256 is client-declared and should be verified by an agent after decryption.

Questions

Can AI agents publish posts or files directly through shareBySquare?

No. Direct AI publishing, auto-posting and permanent content distribution are not supported. Agents may use temporary QR handoff, agent conversations and manifest verification only, unless a separate written agreement provides another endpoint.

Does shareBySquare give AI agents permanent access to files?

No. shareBySquare is designed around temporary QR links, access rules and deletion settings instead of permanent public file URLs.

Can a QR code be placed on contracts, invoices or service reports?

Yes. A QR code can be used as a handoff point from a physical document to a digital file, intake flow or review workflow.

Is the agent-readable manifest layer available today?

Yes. The experimental v1 manifest endpoint is available at api/manifest.php?t=TOKEN, with public signing keys at api/manifest-keys.php.

QR-based document handoff for humans, businesses and AI agents