SDK entry points

Public JavaScript exports and the Solidity integration package.

Monad testnet; not audited. Start with Developers / SDK for installation, configuration and a working example for every public entry point.

ImportPublic helpers / purpose
@bondrail/sdkRoot re-exports: ABIs, client, triggers, permits, x402 seller, data and credit
@bondrail/sdk/abisGenerated factory, account, bond, covenant, earner, vault and credit registry ABIs
@bondrail/sdk/clientbondrailClient, readBondTerms, Tier, MilestoneMode
@bondrail/sdk/permitsignAccountPermit: EIP-2612 with the account as spender
@bondrail/sdk/x402handlePaidRequest, exactUsdcRequirements, httpFacilitator, settleThroughAccount, manifest helpers
@bondrail/sdk/x402-guardbondrailGuard, isBondrailAccount, pinFromBond: check offers before signing
@bondrail/sdk/datacalculateScore, indexedScore, graphql, scorePolicy, NansenClient
@bondrail/sdk/creditcreditLine, getCreditProfile, creditAttestationLabel and attestation types/domain
@bondrail/sdk/yieldimpliedYield: trailing-revenue projections, not promised returns
@bondrail/sdk/triggerparseTriggerTerms: validate optional trigger inputs

The root does not re-export yield or x402-guard; use their subpaths. bondrailClient writes simulate, pad gas, submit and wait for a successful receipt. settleThroughAccount returns a hash instead: callers must wait for and check the receipt. Token approvals are separate. No convenience client method exists for every ABI function: use viem with the relevant ABI for template deployment, vault operations, Funding withdrawal or registry administration.

@bondrail/contracts is a Solidity source package, not a JavaScript entry point. It includes BondrailEarner, BondrailTypes, IBondrailVault, IBondrailCreditRegistry and the protocol implementations. See Native integration for review requirements.