Zodiacs SDK.

One registry. Many surfaces.

The SDK gives apps a stable way to recognize the Twelve, understand where each representation belongs, read public ownership, and shape that state into identity surfaces.

Verified facts for symbolic products.

Four common integrations.

These are the core paths most apps need: verify an address, show provenance, read public holdings, and compute display-ready context.

import {
  getRepresentationByAddress
} from "@zodiacs/sdk";

const representation = getRepresentationByAddress(
  "0x3ffB5282F5891Dd8c813E64059EdB0607537eC91"
);

console.log(representation?.sign);  // "aries"
console.log(representation?.chain); // "base"
console.log(representation?.kind);  // "bridged"

import {
  getBaseZodiacRepresentation,
  getNativeCounterpart
} from "@zodiacs/sdk";

const baseAries = getBaseZodiacRepresentation("aries");
const origin = getNativeCounterpart(baseAries.address);

console.log(origin?.chain);   // "solana"
console.log(origin?.kind);    // "native"
console.log(origin?.address); // Solana SPL mint

import { Connection, PublicKey } from "@solana/web3.js";
import { createPublicClient, http } from "viem";
import { base } from "viem/chains";
import {
  getBaseZodiacsOwnership,
  getSolanaZodiacsOwnership
} from "@zodiacs/sdk";

const connection = new Connection("https://api.mainnet-beta.solana.com");
const solanaOwner = new PublicKey("...");

const solana = await getSolanaZodiacsOwnership(connection, solanaOwner);

const publicClient = createPublicClient({
  chain: base,
  transport: http()
});
const baseOwnership = await getBaseZodiacsOwnership(
  publicClient,
  "0x..."
);

console.log(solana.heldSigns);
console.log(baseOwnership.heldSigns);

import { getZodiacIdentityContext } from "@zodiacs/sdk";

const context = getZodiacIdentityContext(ownership, {
  sunSign: "leo"
});

console.log(context.heldSigns);
console.log(context.elementComposition);
console.log(context.currentSeasonHeld);
console.log(context.wheelCoverage);

Display-ready facts, not horoscopes.

The SDK computes symbolic context from verified public ownership. Apps decide how to present that context; the SDK keeps the source data factual and repeatable.

Styled component preview CosmicReceiptCard

SDK input getCosmicReceiptData(ownership)

Try it live getRepresentationByAddress(address)

Address

Verification Loading official registry... Read-only local check

Aries

Gemini

Leo

Pisces

Sample Cosmic Receipt

A public Zodiac shelf.

Held signs 4 of 12

Wheel coverage 33.33%

Element mix Fire · Air · Water

Season Represented

Native 2 Solana

Bridged 2 Base

Aries Gemini Leo Pisces 8 open

Copy receipt data

The useful surfaces at a glance.

The package is organized around registry facts, representation provenance, public reads, and identity composition.

Built quietly into many kinds of experience.

The SDK is app-neutral infrastructure. It can support astrology interfaces, horoscope products, wallet views, galleries, profiles, identity layers, share cards, public shelves, Cosmic Receipts, Zodiac Wheels, and AI astrology assistants.

A small install surface.

Use the package when a product needs the official registry, address verification, read-only ownership, or display-ready symbolic context.

npm i @zodiacs/sdk

Read-only by design.

The SDK is made for recognition, verification, metadata, public reads, and identity context. It does not request private keys, provide custody, sign messages, submit transactions, provide approval helpers, or move assets.