Creator Quickstart

Ready to publish your first API to Tapistry? This guide summarizes the complete creator flow—from signing in and scaffolding a project to pricing, promotion, and monitoring. Prefer Markdown? The full reference lives in docs/guides/CREATOR_QUICKSTART.md.

1. Authenticate the CLI

pnpm add -g @tapistry/cli
tapi login --backend https://www.thetapistry.com/api

Delete ~/.tapistry/auth.json or rerun tapi login when rotating credentials or switching environments.

2. Scaffold and Configure

tapi init my-first-api --template python-fastapi
cd my-first-api

Update tapistry.yaml with marketplace metadata (publish channel, pricing, dependencies) and verify any `egress.allowlist` entries cover outbound destinations your API needs.

3. Implement Code and Tests

Keep Pydantic models strict, redact sensitive outputs, and ensure your tests/ suite covers both success and failure paths—the publish pipeline enforces minimum coverage.

pip install -r requirements.txt
pytest tests/ -v

4. Secure Credentials

Choose between Platform-Managed Keys, Developer-Managed Keys, or User-BYOK. Upload DMK secrets through the dashboard under Tools → Credentials, and reference them as environment variables or mounted files.

5. Publish to Edge

tapi publish --channel edge
tapi pipeline my-first-api --watch
python scripts/ops/healthcheck.py --backend-url https://www.thetapistry.com/api --json

Builds run containerization, automated tests, security scans, and policy checks. Fix any failures before proceeding.

6. Promote to Stable

tapi promote --api my-first-api --version 0.1.0 --channel stable
tapi pipeline my-first-api

Confirm dependent APIs are still healthy via the dashboard dependencies tab and review contract test results before promotion.

7. Finalize Pricing & Categories

Set pricing, free tiers, and category tags in tapistry.yaml or via the dashboard so consumers can discover and subscribe to your API. Stripe Connect handles payouts once you complete onboarding.

8. Monitor & Iterate

  • Track invocations, latency, and error rates in the analytics dashboard.
  • Subscribe to SLO/alert notifications for regressions.
  • Use audit logs to review security-sensitive events.

Next steps

  • Automate releases in CI by running tapi validate, tapi build, tapi test, and a final tapi publish.
  • Read the Publish Workflow guide for deeper pipeline details.
  • Share the upcoming Consumer Quickstart with your customers so they can adopt your API faster.