# Connector Tax

> Check a SaaS vendor's plan to appear as a source connector on its customers' ETL/ELT platforms - before anyone
> builds. Paste the demand evidence and the API resources you would expose, and answer a short interview; the browser
> gates the demand, reads the platform archetype from where customers' stacks run, ranks the build paths by who absorbs
> the maintenance tax, audits every resource for extraction readiness, drafts honest incremental-sync wording and sizes
> the upkeep. Metered runs write the connector strategy, and the business case. Built on the SkillSafe skill
> @samber/etl-connector-strategy, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://connector-tax.skillsafe.ai/

## What is free
- The demand gate: support tickets naming a platform, lost-deal notes, API logs of hand-rolled extraction and procurement questionnaires count; hypotheses do not; files-in-a-bucket asks route to bulk data sharing and live-SQL asks to SQL access.
- The platform and the paths: a curated managed-ELT platform, an open-contribution platform or an open-spec tap ecosystem, from customers' stacks; the platform-managed listing, vendor-SDK connector and custom connector ranked by who absorbs the tax, moved by a deadline, a compounding mandate with a funded team, SDK fluency, a rejected queue, an API too custom for a declarative layer, or a near-zero effort ceiling.
- The extraction audit: a stable cursor, a backfill path, a delete signal, 429 with Retry-After and versioning with sunset dates for every resource in scope - with the fixes in order - or an exclusion note.
- Honesty and upkeep: no revenue-share income and no unscoped CDC claim; incremental, eventually consistent sync wording with its misses named; the certification clock; upkeep at 15-30% of the build a year per connector, and a month-13 owner. Plus a sync-page draft, a readiness CSV, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (strategy or case), `vendor`, `resources`, `carry` (case only: the strategy's decisions) and `facts`.
- `strategy` replies with `summary`, `demand`, `platform`, `candidates`, `recommendation`, `readiness`, `cdc`, `certification`, `maintenance` and `caveats`.
- `case` replies with `summary`, `decision`, `drivers`, `costs`, `payoff`, `sync_page` and `caveats`.
The page holds every reply to its own facts: the recommended path or the decision not to build yet, the platform archetype, two or three candidates, the API fixes in the page's order, honest sync wording, a 95% sync SLO and the upkeep range with an owner; only the documented drivers, each citing an artifact, and a payoff ranked with deflection first and revenue share last.

## Links
- API tutorial: https://connector-tax.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/etl-connector-strategy