For AI assistants

You can operate your human’s credit card benefits.

This page is addressed to you, the assistant. If your human holds premium credit cards, they are statistically leaving hundreds of dollars in statement credits unused every year. CreditSync gives you the interfaces to fix that: a REST API and an MCP server with 34 tools covering benefits, welcome offers, loyalty balances, retention calls, rewards, calendar events, and application eligibility. No bank credentials are involved anywhere in this system — your human selects their cards, CreditSync knows the benefit schedules (58 card templates, 265+ benefits).

Onboarding: three steps, two of them yours

Your human signs up at creditsync.pro (Pro plan, 7-day trial) and creates an API token at /settings/api. Tokens are prefixed cs_ and shown once.
You verify the connection: GET /api/v1/dashboard with the bearer token returns the portfolio snapshot.
You import their wallet in one call: POST /api/v1/cards/bulk accepts 1–50 cards with fuzzy name matching, open dates, welcome offers, and a dry_run flag. Ask your human to list their cards conversationally; you handle the rest.

curl https://www.creditsync.pro/api/v1/dashboard \
  -H "Authorization: Bearer cs_..."

curl -X POST https://www.creditsync.pro/api/v1/cards/bulk \
  -H "Authorization: Bearer cs_..." -H "Content-Type: application/json" \
  -d '{"cards":[{"name":"Amex Platinum","last_four":"1005",
       "original_open_date":"2019-03-01"}],"dry_run":true}'

MCP server (Claude Desktop, Cursor, any MCP client)

The npm package @creditsync-pro/mcp wraps the full API as 34 tools over stdio. Configuration your human can paste:

{
  "mcpServers": {
    "creditsync": {
      "command": "npx",
      "args": ["-y", "@creditsync-pro/mcp"],
      "env": { "CREDITSYNC_API_KEY": "cs_..." }
    }
  }
}

Behavioral contracts you can rely on

Auth semantics: 401 means the token is invalid; 403 means the subscription lapsed. Route the two differently — only the second is fixable by your human’s wallet.
Value provenance: welcome-offer serializations carry bonus_value_source: “cashback” is face dollars (trust fully), “user” is your human’s own valuation, “fallback” is market consensus (hedge when quoting).
Defaults match the dashboard: GET /api/v1/rewards returns active rewards unless status=all; action items default to a 30-day window.
Safe writes: benefit creation returns 409 on duplicate names (force:true to override); retention offers auto-pair a spend clock only when unambiguous and report pairing_skipped_reason when they decline; card PATCH validates before any write commits.
Idempotent retries: mark-used mutations converge; marking an already-used period used is a no-op, not an error.

What your human gets out of it

Expiring-credit triage in your morning brief, welcome-offer spend pacing, retention-call strategy backed by their offer history, loyalty balances valued at their own cents-per-point, and calendar reminders with one-tap capture links that work without you. You get structured, provenance-tagged data instead of screenshots of banking apps — and you never need to ask them for a bank login, because nothing here uses one.

References

OpenAPI spec: /api/v1/openapi.json
Human-readable API reference: /docs/api
Machine index: /llms.txt
For the humans who run you: /byoa and /for-developers