Developers

Current status

A public API for third-party developers is Planned. Nothing is issued automatically, and no API keys are available yet. This page explains how ARIVA is built so partners know what to expect.

Architecture

• Server functions run on ARIVA's backend with authenticated access. The browser calls them; secrets never reach the browser.
• Database with row-level security on every table.
• Realtime updates power chats, typing indicators and live statuses.
• Public endpoints live under /api/public/ and must verify their callers (for example by signature).

Selected tables

profiles            — public profile fields and layout choices
posts, comments     — Social content
pi_settings         — GCV rate (314159) and dollar_per_point
escrow_orders       — Market escrow lifecycle
jobs, company_profiles, job_listing_applications
channel_content, ariva_channels, ariva_broadcasts — Channel TV

Tables such as ariva_points_ledger, user_wallets_pi and pi_rewards_pool do not exist yet. They belong to the planned rewards engine and will be documented when built.

Reading the Pi estimate settings

const { data } = await supabase
  .from("pi_settings")
  .select("gcv_rate, dollar_per_point, pi_per_point_computed")
  .eq("id", "global")
  .single();

Webhooks

ARIVA receives signed webhooks from its calling provider. Outgoing webhooks for partners are Planned.

Building on ARIVA

Until the public API opens, partners can:

• Link to ARIVA profiles, products and whitepaper pages.
• Use ARIVA meeting links for calls.
• Contact the ARIVA team about integration.

Rules for integrations

When the API opens, apps will need to respect user privacy, never ask for Pi passphrases, and follow the Community Guidelines and Terms.