Install Jentic One Beta

Connect the SendSafely REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendSafely REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendsafely.com%2Fsendsafely" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendsafely.com%2Fsendsafely" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SendSafely REST API.

Verify API credentials

Get user information

Add dropzone recipient

Query and filter SendSafely REST API records by parameters

Monitor SendSafely REST API operational status and events

GET STARTED

Start building with SendSafely REST API

Explore with Jentic One

View OpenAPI Document

Automated config Management

Automate config operations by combining multiple SendSafely REST API endpoints. Agents can verify API version and then get user information in a single workflow.

Call GET /config/version/{platform}/{versionNo}/ to verify API version, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SendSafely REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'verify API credentials', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

36 endpoints — the sendsafely rest api provides programmatic access to sendsafely for sending and receiving encrypted files.

METHOD

PATH

DESCRIPTION

GET

/config/verify-credentials/

Verify API credentials

GET

/config/version/{platform}/{versionNo}/

Verify API version

GET

/user/

Get user information

GET

/user/dropzone-recipients/

Get dropzone recipients

PUT

/user/dropzone-recipients/

Add dropzone recipient

GET

/user/groups/

Get contact groups

GET

/enterprise/

Get enterprise information

GET

/package/

List active packages

GET

/config/verify-credentials/

Verify API credentials

GET

/config/version/{platform}/{versionNo}/

Verify API version

GET

/user/

Get user information

GET

/user/dropzone-recipients/

Get dropzone recipients

PUT

/user/dropzone-recipients/

Add dropzone recipient

GET

/user/groups/

Get contact groups

GET

/enterprise/

Get enterprise information

GET

/package/

List active packages

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring SendSafely by hand means putting your own hostname into the base URL, sending the ss-api-key header, and computing the HMAC-SHA256 request signature and timestamp for every call yourself. Through Jentic you install once, import SendSafely from the API Directory, store the key and secret once, and your agent calls it.

Permission scoping

SendSafely puts the package id in the URL path (/package/{packageId}/...), so a rule can pin your agent to one package: it can read that package's files and activity and nothing else. You choose the operations it may call, so file deletion or package finalize is not included unless you add it.

Credential isolation

Your SendSafely key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'verify API credentials' or 'list files in a package', and Jentic returns the matching SendSafely operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SendSafely REST API through Jentic.

What authentication does the SendSafely REST API use?

The SendSafely REST API uses an API key passed in the `ss-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I verify API credentials with the SendSafely REST API?

Yes. Use the GET /config/verify-credentials/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SendSafely REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I verify API credentials through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verify API credentials'. Jentic returns the matching SendSafely REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the SendSafely REST API have?

The SendSafely REST API exposes 36 endpoints covering config, user, enterprise operations.

Can I limit what my agent is allowed to do with the SendSafely REST API?

Yes. Jentic One is self-hosted by you, so your own rules decide which SendSafely operations and credentials the agent may use. Because SendSafely puts the package id in the URL path (/package/{packageId}/...), you can pin the agent to a single package so it only reads that package's files and activity and nothing else. You pick the operations it may call, so actions like file deletion or package finalize stay out of reach unless you add them.

SendSafely REST API

Name: SendSafely REST API
Brand: SendSafely REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyStorageObject StorageapiKey36 EndpointsREST

For Agents

Programmatically verify API credentials, verify API version. Covers 36 operations with apiKey authentication.

Use for: I need to verify API credentials, I want to verify API version, Search for user information, Find all dropzone recipients

Not supported: Does not handle payments, communications, or crm - use for storage and databases only.

The SendSafely REST API provides programmatic access to SendSafely for sending and receiving encrypted files. The API uses API key and HMAC signature-based authentication. The base URL is your SendSafely host (e.g. https://companyname.sendsafely.com or https://www.sendsafely.com) followed by /api/v2.0. The API exposes 36 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the SendSafely REST API to your agent

Capabilities

Start building with SendSafely REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SendSafely REST API