From ENJU holdings to AI credits.

Each trade contributes a 2% fee in ETH: 70% funds holder allocations and 30% supports builders. OpenRouter provides access to AI models through one API. An issued key lets you spend credit in compatible applications and coding tools.

Earned allocation

Your recorded share of a completed day’s ETH fees.

Claimable allocation

Earned ETH you have not yet converted into an API key.

Available AI credit

Unspent OpenRouter credit on an issued, active key.

• Only individual trader and holder wallets count. Treasury, liquidity-pool, exchange, and burn addresses are excluded from eligibility and eligible supply.
• Each wallet is assessed separately. Transfers change each wallet’s balance from the time of transfer; balances and holding history are not combined across wallets.
• Buying just before midnight only counts for the time actually held. There is no separate requirement to hold continuously for 24 hours.

Illustrative example: holding 200,000 ENJU for 12 hours and zero for the other 12 hours gives a daily average of 100,000 ENJU. Holding 100,000 for only half the day gives an average of 50,000 and does not qualify.

A sale changes your average balance for the day in progress and later days. It does not change completed daily allocations or unused credit on active keys. Claim from the wallet that earned the allocation, even if its current ENJU balance is zero.

1. Connect the earning wallet and choose from its unclaimed allocations.
2. Review the included days, daily averages, recorded fees, claimable ETH, conversion quote, and net credit. Amounts above the $200 key limit remain claimable through additional claims.
3. Authorize the claim with a gasless EIP-712 wallet signature. No token approval or transfer is required.
4. Allow a few minutes for conversion and key setup, then copy the key shown once. Delivery time is an estimate.

A failed claim can be retried without losing its allocation. There is no daily claim deadline. Review the ETH amount and net OpenRouter credit in your quote before signing.

Of the revenue Enju receives under agreements with supported projects, 100% funds ENJU buybacks and burns. Each project’s revenue-sharing terms are negotiated separately. This revenue is separate from the 70/30 trading-fee split.

Support depends on treasury resources. Follow the official Enju account for builder application details, buyback updates, and execution references.

• Daily records: UTC period, block references, time-weighted eligible balances, total eligible averages, and collected ETH fees.
• Treasury records: fee inflows, the 70/30 split, and transaction references. Holder claim records are not part of the public protocol data.
• Credit value varies with trading activity and conversion. AI credit is consumable access, not a guaranteed cash return.
• Network, conversion, OpenRouter, and model-provider availability can delay delivery or usage.

Use the official account to verify the ENJU token contract, treasury address, Pons page, builder application form, support channels, and buyback references. Check addresses and links before connecting or signing.

Start by detecting your tools and previewing the configuration changes. Usage and bulk-setup snippets continue from the setup example below.

pnpm add @enjucredit/sdk

import { Enju } from '@enjucredit/sdk'

const enju = new Enju()
const apiKey = process.env.OPENROUTER_API_KEY!

const detected = await enju.harness.detect()
const preview = await enju.harness.configure({
  harness: 'codex',
  apiKey,
  scope: 'user',
  dryRun: true,
})

console.log(detected)
console.log(preview.changed)

// Apply the same reviewed input
await enju.harness.configure({ ...preview.input, dryRun: false })

const usage = await enju.key.usage({ apiKey })

console.log({
  limit: usage.limit,
  used: usage.used,
  remaining: usage.remaining,
  expiresAt: usage.expiresAt,
})

const status = await enju.harness.status({ harness: 'codex' })
console.log(status.configured, status.model)

const installed = (await enju.harness.detect())
  .filter((tool) => tool.installed)
  .map((tool) => tool.harness)

await enju.harness.configureAll({
  apiKey,
  only: installed,
  scope: 'user',
  dryRun: false,
})

// Removes Enju-managed settings without deleting unrelated config
await enju.harness.remove({ harness: 'codex', scope: 'user' })