Developer APIs on Giga3

Two separate HTTP surfaces on Giga3 AI: a read-only GigaSocial integration API (platform key) and a Premium user API (per-account keys). Only the endpoints listed below are live today.

GigaSocial read API

Read-only GET routes for public GigaSocial content — feeds, posts, profiles, and comments. Intended for dashboards, research tools, and integrations.

Base URL

https://perfect-lark-521.convex.site/gigasocial/api/v1

Authentication

Protected routes require a platform API key configured on the Convex deployment as GIGASOCIAL_DEVELOPER_API_KEY. Pass it on every request using either header:

Authorization: Bearer YOUR_PLATFORM_KEY
# or
X-Giga3-Api-Key: YOUR_PLATFORM_KEY

Rate limit: 120 requests per hour per key. Contact [email protected] to request a production platform key.

Endpoints

GET/healthPublic

API liveness and endpoint list (no key required).

GET/post?id={postId}Platform key required

Fetch a single public post by Convex post id.

GET/feed?limit=20&cursor=&community=Platform key required

Paginated public community feed (cursor = createdAt ms).

GET/discover?filter=trending&q=&limit=24Platform key required

Discover posts. Filters: trending, recent, education, creator, ai, video, photo, music.

GET/profile?handle={handle}Platform key required

Public creator profile and recent posts by @handle.

GET/comments?postId={postId}Platform key required

List comments on a public post.

Example — public feed

curl -s \
  -H "Authorization: Bearer YOUR_PLATFORM_KEY" \
  "https://perfect-lark-521.convex.site/gigasocial/api/v1/feed?limit=5"

Premium user API

Active Premium subscribers can create personal API keys (hashed server-side, max 5 active keys). Today only GET /api/v1/health and GET /api/v1/me are implemented. Additional scopes (chat write, GigaLearn, media read) are reserved for future routes — not available yet.

Base URL

https://perfect-lark-521.convex.site/api/v1

Authentication

Pass your user key (prefix giga3_sk_…) via Authorization: Bearer or X-Giga3-Api-Key. Keys require an active Premium subscription (api_access entitlement). Create keys below when signed in with Premium — scopes beyond chat:read are reserved for future routes.

Live endpoints

GET/healthUser key required

Key validation and scope discovery for your user API key.

GET/meUser key required

Returns your user id, key prefix, and granted scopes (requires chat:read scope).

Manage your API keys

Loading…

Example — verify key

curl -s \
  -H "Authorization: Bearer giga3_sk_YOUR_KEY" \
  "https://perfect-lark-521.convex.site/api/v1/me"

Security & privacy

GigaSocial routes are read-only GET — no writes through either API surface.
Only public GigaSocial posts and profiles are returned; followers-only content is omitted.
Never embed platform or user API keys in client apps, PWAs, or public repos.
GigaSocial platform keys: 120 requests/hour. User keys: usage tracked per key/day on the server.
Use HTTPS only. Revoke compromised user keys via apiKeys.revokeKey when signed in.

Both APIs are served from the Convex site URL above. A dedicated hostname (for example api.giga3ai.com) would require infrastructure changes — the documented paths are the supported base today.

GigaSocial error codes

HTTP	code	Meaning
401	`unauthorized`	Missing or invalid platform API key
404	`not_found`	Post, profile, or resource not public
429	`rate_limited`	Hourly quota exceeded — back off and retry
503	`api_not_configured`	GigaSocial developer API disabled on this deployment

GigaSocial responses use JSON with ok: true on success. User API responses return ok: true with your user id and scopes on /me, or ok: false with an error message when the key is missing, revoked, or lacks the required scope.