Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add apideck-libraries/api-skills --skill sage-intacct-restgit clone --depth 1 https://github.com/apideck-libraries/api-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/apideck-libraries/api-skills/sage-intacct-rest)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/sage-intacct-rest"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/sage-intacct-rest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/sage-intacct-rest"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/sage-intacct-rest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00072 | $0.01811 |
| Opus 5.5 | $0.00029 | $0.00724 |
| Sonnet 5.5 | $0.00014 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
sage-intacct-rest scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 20d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl 'https://unify.apideck.com/proxy' \ How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sage Intacct REST (via Apideck Proxy)
Access Sage Intacct REST through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Sage Intacct REST's native API — you keep using Sage Intacct REST's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.
Auth-only / proxy-only connector. Apideck does not map Sage Intacct REST to a unified-API resource model — your code talks Sage Intacct REST's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.
Quick facts
- Apideck serviceId:
sage-intacct-rest - Mode: Proxy-only (no unified API resources)
- Auth type: oauth2
- Status: live
- Apideck setup guide: OAuth credentials
- Gotchas: page
- Sage Intacct REST docs: https://developer.intacct.com/api/
- Homepage: https://www.sageintacct.com/
At a glance
- Implementation difficulty: involved — Paid Web Services Developer License + Per-Consumer Admin Authorization Required
- Vendor partnership required: yes (Sage Intacct Marketplace) — A Sage Web Services developer license is required — via the Sage Intacct Marketplace Partner Program, or directly from Sage through your account manager.
- Apideck-managed credentials: available — For testing and evaluation: consumers authorize against Apideck's registered Sage application, so the consent screen shows Apideck branding.
- Account type required: Sage Intacct company with a Web Services subscription
- Consumer access level: The connection inherits the authorizing Sage Intacct user's role permissions, and a company Admin must authorize the application in each consumer's company.
- Sandbox: available — Registering a Non-production OAuth app is free; a Sage Intacct sandbox company itself is a paid, licensed feature, gated by eligibility and not self-serve.
- Costs: Sage Intacct Marketplace Partner Program membership is $2,500/year, plus $0.015 per API call once your consumers are live. Effective August 2026.
- Rate limits: Sage Performance Tier 1: 100,000 API transactions/month per company, shared with the XML API. Over-limit: 429 (GW-0010). Headroom: x-downstream-ratelimit-*.
- Authentication: Authorization Code grant, a real OAuth flow, unlike the sage-intacct (XML) connector, which uses a Sender ID plus company/user credentials.
- Webhooks: Virtual webhooks — created, updated and deleted events across 13 of the supported accounting resources. Sage Intacct has no native webhooks.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 20d ago Changed 685571be3d3a
- 1mo ago First seen · 106 lines · 72 tokens per session scan A 271999753416
sage-intacct-rest is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 1,811 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
inngest-realtime
Use when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the browser, log tailing for long-running jobs, or human-in-the-loop approval flows that publish a prompt and wait for a user reply. Covers Inngest v4…
inngest-durable-functions
Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where…
inngest-events
Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema…
inngest-setup
Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express…
inngest-brownfield-audit
Use when analyzing an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest. Covers repository discovery, framework and package detection, finding durability gaps in HTTP handlers, webhooks, cron jobs, queues, long-running jobs, AI agents, Agent Evals, polling loops, eval loops, and…
inngest-middleware
Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly…