Typed operations should follow the contract—not invent a second API.

Official SDK availability, package names and supported runtimes will be published only after the generated clients pass release and security checks. The example below demonstrates intended shape, not an installable package claim.

Review REST API Read Documentation

Nothing publishes without approvalPaid product accessNo ranking guarantees

Release status

No public SDK package is claimed as released on this page yet.

Distribution

Verify package provenance before installing.

Published SDK documentation will name registry, package, checksum or signature policy, supported runtime and API compatibility. Do not install similarly named unofficial packages.

Illustrative TypeScript

Explicit client, environment and site context.

const client = new SEOForge({ token: process.env.SEOFORGE_TOKEN });
const runs = await client.runs.list({ siteId: "site_123" });
// Illustrative only — package not publicly claimed.

Authentication

Server-side service tokens only.

Load a scoped token from a secret manager. Never bundle it into browser JavaScript or commit it to source.

Scopes

Types do not expand token authority.

Read clients remain read-only
Request methods require explicit runs:request
Workspace, site and environment are checked server-side
No approval, merge, deploy, credential or bypass method exists

Rate limits

SDK helpers should expose—not hide—control flow.

Read limit headers, honor Retry-After, use idempotency where supported and bound retries. Plan capacity still applies.

Errors

Catch typed categories and retain request IDs.

try { /* request */ } catch (error) {
  // inspect error.code, error.status, error.requestId
}

Security boundary

SDKs can never approve, merge, deploy, retrieve credentials or bypass protection.

Paid deployment · human authority

SDK access follows paid workspace authorization.

Use the REST contract today only where current documentation confirms it.

Choose Your Plan Book a Demo