@fillgate/core
v0.3.1
Published
Venue adapters with fee codes baked in, guardrails, fee ledger, geoblock. Zero runtime deps; venue SDKs are optional peers loaded lazily.
Readme
@fillgate/core
Venue adapters with fee codes baked in, plus the guardrails, fee ledger and geoblock that sit in
front of them. Zero runtime dependencies; venue SDKs (@solana/web3.js, @polymarket/clob-client-v2,
@nktkas/hyperliquid, viem) are optional peers, loaded lazily only for the venues you enable.
Most people want @fillgate/mcp — the MCP server
that exposes these adapters as tools to Claude and other agents. Use @fillgate/core directly only
if you are embedding the adapters in your own app.
import { loadConfig, enabledVenues, JsonlLedger } from '@fillgate/core'
const config = loadConfig(process.env) // reads DRY_RUN, MAX_NOTIONAL_USD, MAX_SLIPPAGE_BPS,
// RATE_LIMIT_PER_MIN, FILLGATE_VENUES, venue credentials
enabledVenues(config) // ['jupiter', ...] — only fully configured venues
const ledger = new JsonlLedger(config.ledgerPath) // daily YYYY-MM-DD.jsonl event files
ledger.readAll() // prepare / execute_attempt / fill / preview / guard_rejection
ledger.summary() // fills only — the fee-reconciliation viewEvery money-moving path is two-step (prepare → execute) and passes through the guardrails in
guards.ts. DRY_RUN=true (the default) never broadcasts.
Docs: github.com/mineloop99/fillgate · MIT
