Show us what you built.

Agent first. Human-reviewed.

Submissions require a Deepline account or API key. Agents can assemble the first draft, but every HubSpot submission is reviewed before it becomes a gallery entry.

Include

• A repo or live app URL
• Screenshots, YouTube, Loom, or product captures
• The problem before Deepline
• The workflow, API path, repo path, or review flow
• A result: time saved, records fixed, workflow reused

Agent submit

Claude Code can submit over the API with a local Deepline auth context. The endpoint is authenticated, hash-deduped, protected by bot checks, and limited before it forwards anything to HubSpot.

You are in my project repo. Prepare and submit this project to Deepline's Built with Deepline gallery.

First inspect the repo, README, screenshots/assets, demo links, and any Deepline workflow or API usage. Then write a concise submission that explains what the project does, what problem it solves, why it was built, how Deepline was used, and what changed after.

Endpoint:
POST https://deepline.com/api/built-with-deepline/submit

Headers:
Authorization: Bearer $DEEPLINE_API_KEY
Content-Type: application/json

Secret handling:
- Read DEEPLINE_API_KEY only from the local environment or an existing authenticated Deepline CLI/session.
- Do not paste an API key into source files, README files, issue comments, screenshots, logs, or the submitted JSON body.
- If no API key or authenticated session exists, stop and ask the user to authenticate first.

Constraints:
- Use one submission per finished project.
- Include at least one live app URL or repo URL.
- Include screenshot, YouTube, Loom, public Drive, Figma, Arcade, Supademo, or asset URLs, one per line.
- Deepline rejects duplicate payload hashes and limits each authenticated identity to 5 submissions per 24 hours.
- Submissions go into a HubSpot form review queue. Nothing is published until Deepline approves it.
- Do not invent metrics. If impact is qualitative, say so plainly.

JSON body:
{
  "projectName": "",
  "projectType": "gtm-agent",
  "websiteUrl": "",
  "repoUrl": "",
  "youtubeUrl": "",
  "loomUrl": "",
  "demoVideoUrl": "",
  "screenshotUrls": "",
  "problemStatement": "",
  "whyBuilt": "",
  "deeplineWorkflow": "",
  "impact": "",
  "builderName": "",
  "builderRole": "",
  "company": "",
  "linkedinUrl": "",
  "twitterUrl": "",
  "githubUrl": "",
  "youtubeProfileUrl": "",
  "preferredLinkUrl": "",
  "githubStars": "",
  "communitySignal": "",
  "email": ""
}

Create an API key from Dashboard API keys, then store it in your local shell or secret manager. Do not paste the key into the prompt or project files.