Gate/AI for React Native

Install the SDK

React Native 0.81 is the development baseline. The SDK is distributed from its public GitHub repository and pinned to a release tag; it is not on the npm registry. Install pods and rebuild the native app after adding the SDK. Expo requires a custom development build; Expo Go cannot load this native module.

From your app directory:

npm install github:GateAI-net/gate-react-native#1.0.0
cd ios && pod install

npm builds the package from source on install, so Node 22 or later is required on the machine running npm install. Releases are listed at github.com/GateAI-net/gate-react-native/releases.

Configure a client

Replace the tenant URL, Apple Team ID, and Android signing fingerprint with your registered values. Supply both platform configurations for a shared app. The Google Cloud project number is a decimal string.

import { GateAIClient, GateAIError } from '@gateai/react-native';

const client = await GateAIClient.create({
  baseUrl: 'https://your-team.in.gate-ai.net',
  ios: { teamIdentifier: 'ABCDE12345' },
  android: {
    signingCertSha256: 'YOUR_64_HEX_CHARACTER_SHA256_FINGERPRINT',
    cloudProjectNumber: '123456789012',
  },
});

iOS detects the bundle identifier automatically; Android uses the host app’s package name. On Android, deviceIdentifierEnabled is false by default. Use the native setup checklist below for attestation and development tokens.

Make your first request

Choose a model enabled for your gate and send a JSON request. The SDK adds authentication and signs the request on-device.

try {
  const response = await client.request({
    path: 'openai/chat/completions',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      model: 'your-enabled-model',
      messages: [{ role: 'user', content: 'Hello from Gate/AI' }],
    }),
    context: { userTier: 'pro', appFeature: 'chat' },
  });
  const completion = JSON.parse(response.body);
  // Use completion in your app.
} catch (error) {
  if (error instanceof GateAIError && error.status === 429) {
    const retryAfter = error.header('Retry-After');
    // Show a usage-limit message or schedule a retry.
  }
  throw error;
}

// When the owning service is permanently torn down:
await client.dispose();

For GET requests, set method to 'GET' and omit the body. Reuse the client across requests.

Supported APIs & behavior

request

Send GET or POST requests with UTF-8 text or JSON bodies. Responses are buffered and include status, headers, and body. Authentication, token refresh, and one retry on a DPoP nonce challenge are handled for you.

authorizationHeaders

Generate headers for your own HTTP client using a relative path, method, and optional nonce. Send to the exact configured origin and path. Custom transports must handle a 401 DPoP-Nonce challenge and obtain a fresh proof for the retry; never cache or reuse proofs.

Per-request context

Set userStatus, userTier, userIdentifier, appFeature, and quotaAnchorDay (1–31). Use an opaque user ID. Explicit headers override context values; authentication headers cannot be overridden. Analytics reference →

clearCachedState & dispose

Clear the cached access token to authenticate again, or dispose of a client you no longer need. Neither operation deletes device keys. Requests already in flight can finish after disposal.

Current limits

Use an HTTPS origin and relative request paths. Query strings, fragments, percent escapes, and dot segments are not supported. The request API does not support binary payloads, streamed responses, or cancellation. These SDKs target native iOS and Android only.