Integration overview

There are five realistic integration paths. Choose based on what you are building, not on what sounds familiar.

​

REST storage API

This is the primary path. It is company-scoped, API-key authenticated, and documented in the API reference. Use it when:

• you control a server,
• you need deterministic storage semantics,
• you want scopes and bucket restriction,
• you can keep a secret in a secret manager.

Do not use it directly from a browser. API-key headers are not CORS-allowed. See Requests and CORS.

​

Laravel and PHP

The API is plain JSON over HTTPS, so any HTTP client works. The Laravel guide covers configuration, a small client wrapper, and streaming uploads.

​

Backup agent

The desktop agent is a first-party application that backs up a machine to Everabyte. It uses device-bound keys, not general-purpose developer keys. It is not a documented integration contract for third parties. If you need scheduled backup from a server, use the REST API with your own scheduler.

​

MCP server

The MCP endpoint exposes an authenticated tool surface for AI clients. It requires:

• the mcp scope on the key,
• a paid subscription.

Trial accounts are refused before the MCP handshake. See MCP.

​

S3-compatible gateway

A SigV4 gateway exists and supports common operations, but it is gated by a platform flag and not enabled by default. Do not assume S3 compatibility. See S3 compatibility.

​

Choosing the right path

​

What not to expect

• No official SDK is published at this time. Examples on this site are illustrations.
• No public bucket provisioning API.
• No public sharing or permission API.
• No self-service partner onboarding.
• No guarantee of S3 API parity.

​

Related