Skip to content
Rhea

Integration entry points

Choose the capability your application needs.

Build supported data workflows across customer-chosen systems, or add independent passwordless sign-in. Choose Data for permitted work and Key for authentication.

Start here

Two products. Independent integration paths.

Start with the job you want to build. Each guide shows the request, the expected result and the responsibilities that make the integration work.

Rhea Data

Build with defined data authority.

  1. 1. Configure a supported object-storage connection and customer credentials.
  2. 2. Identify your app and grant only the resources and supported actions it needs.
  3. 3. Use an enabled API operation and review its attributable result.

Check your connector's actual operations. Direct database queries are currently disabled.

Data architecture and API scope

Rhea Key

Add passwordless sign-in.

  1. 1. Choose the current SDK with direct RK-1 or registered OIDC.
  2. 2. Present the QR or device handoff and a site-bound, one-time request.
  3. 3. Verify the proof, expiry and replay protection on your backend before creating a session.

Works without Rhea Data. Start with the RK-1 quickstart, or request the integration package and OIDC registration details for your website.

RK-1 quickstart and OIDC guide
Request Data API access details Request the RK-1 integration package Request OIDC client registration

Technical responsibilities

See what happens behind the user experience.

These models explain which parts belong on the client and which must be verified on your backend. They are schematic—not copy-and-paste API examples.

01

Supported work across connections

Rhea Data

Applications integrate enabled Data API operations under their own identity and granted scope. Keep request checks, execution and attributable results clear; protected-content paths have additional client and connection responsibilities.

Pseudocode · integration responsibilitiesProduct overview
Inspect the schematic responsibilities for Rhea Data
rhea data · conceptSchematic
PSEUDOCODE — not runnable API syntax
identify application
check granted connection + permissions
request permitted operation
handle protected content in authorized client
record activity + usage
return result
02

Standalone passwordless sign-in

Rhea Key

Any participating website or app can integrate Rhea Key without using Rhea Data. Add the sign-in entry with the SDK, issue a site-bound request and verify the response on your backend before establishing a session. Keep replay protection; a button alone is not a complete integration.

Pseudocode · integration responsibilitiesProduct overview
Inspect the schematic responsibilities for Rhea Key
rhea key · conceptSchematic
PSEUDOCODE — presentation only
browser: present sign-in and return proof

backend: bind challenge to requesting site
verify signature + expiry + replay protection
create session only after verification

Shared model

Two products. Different checks.

Who is acting

People, apps and assistants have distinct identities so their activity can be attributed.

Granted access

Authorize a session or assistant connection once. Enforce its scope, log activity and disconnect to revoke further access.

Signatures

Key sign-in proofs require backend verification; Data operations require identity and permission checks.