Developers / Service reference
Each Proxy product is delivered by one or more services. A service has one responsibility, its own scopes and its own meter, and it is the name your integration is granted and your usage records carry. This is the technical catalogue; the products are described for buyers on the product pages.
The rows below are deliberately uniform. Every service answers the same five questions in the same order, so two of them can be compared without reading two differently shaped stories.
In the order the platform lists them, with the products each one delivers. Rates are the platform's standard rates; yours are confirmed before a service is enabled.
Managed document storage scoped to an organisation. Storage class, metadata and retention are yours to set; the size ledger and the audit trail come with it.
Two sub-services sold separately: OCR reads a document into text and structure, and Analysis classifies, extracts, validates, summarises and compares it. Both run as asynchronous jobs.
Signature envelopes with a full status history, templates with merge fields, drawn or typed capture in your own page, custom signing domains, and server-side validation of every submitted signature. What is recorded is the signer reference, the capture method, the timestamps, the status history and the validation result.
Email and SMS sent on the organisation's behalf, with templates, suppressions and a delivery record per message. WhatsApp exists as a channel but is switched off and unpriced. SMS is metered by segment, because that is how carriers charge.
AI customer-care agents answering by SMS and email: knowledge, approvals, controlled workflows and hand-over to a person. Requires Communications, which carries every message.
UK telephone numbers, browser calling for staff in Proxy or in your own CRM, ring groups, warm and cold transfer, recording and call outcomes. A billed minute is the whole call, not one leg of it.
Appointment types, staff availability, Google Calendar connections, booking pages on your own domain, and rescheduling. Reminders are sent through Communications when it is enabled.
Colours, fonts, logos and layout for a business unit's client-facing pages, applied to signing and booking through one resolver. Editing and previewing are free; a unit is charged once it publishes.
Browser capabilities are a closed list, and that is the security property rather than a limitation. A token that could carry an arbitrary scope would be a secret key with a shorter life: something your backend could be talked into minting for anything.
Each capability is minted by your backend for one resource, for a few minutes. The component reads its limits off the token, so page code cannot widen them.
| Capability | Service | What the page may do |
|---|---|---|
| sign.capture | Sign | Draw or type a signature in your page. |
| sign.complete | Sign | Complete a signature request. |
| storage.upload | Storage | Accept files from the person in front of you. |
| storage.download | Storage | Let them read one file back. |
| bookings.book | Bookings | Choose and hold one appointment. |
| bookings.calendar | Bookings | Show one member of staff their own diary. |
| forms.complete | Sign | Fill in and submit a form. |
| documents.view | Sign | Read a generated document, without being able to make one. |
| voice.agent | Voice | Place and answer calls as one member of staff. |
Retention is a business decision, so the class is set per object rather than inferred from how often something has been read lately. The platform defines six classes; Standard is enabled today and the others are not yet switched on. Volume held over time is what is charged; uploads and downloads are counted and free.
Send us the shape of the work. We will name the services that cover it, the operations you would be billed for, and anything on your list that Proxy does not do.