
We built the name.com API so developers can ship domains without the hassle. Today we're launching name.dev: tutorials, partner case studies, endpoint deep dives, and the integration context that API docs don't cover.
What name.dev is
name.dev is a content hub for anyone building on the name.com API or evaluating domain API partners. Our goal is to: help you go from API token to production, fast — and help you build domain experiences that actually convert.
What's here at launch
We're not launching with a landing page and a promise. name.dev opens with a full library of technical content, partner stories, and product updates — all written to help you ship.
Learn
These guides cover the core integration patterns and workflows developers need when building on the name.com API:
- Domain APIs in Python — getting started with code examples
- DNS management — automate configuration and deployments via API
- DNS propagation — understanding TTL, caching, and deployment strategies
- Domain transfers — automate domain migrations programmatically
- MX record configuration — programmatic email routing via the Core API
- WHOIS data — the complete integration guide
- ICANN lookup — search domain data programmatically
- Domain registration in Python — end-to-end with code examples
- CNAME Records: When to Use Them, When to Avoid Them, and Common Pitfalls (Video)
These guides are built to complement the API documentation — they provide the architectural context, decision frameworks, and integration patterns that reference docs don't always cover.
Case studies
Four partner stories from platforms that ship production domain experiences on the name.com API:
- Hercules — went from concept to in-product domains in 3 days using AI coding agents and the OpenAPI spec
- Railway — one product engineer, two weeks, 1,500+ domains per month
- Beacons — tripled paid accounts by bringing domain purchase inside the creator platform
- Riley & Grey — solved a key friction point with 4 API calls — and has been on the name.com API for 13 years
These are implementation stories from the actual developers: what the team built, how long it took, what the business impact looked like, and what they'd tell you if you asked.
Product updates
name.dev is also where we'll publish news, product updates, and changelog highlights for the name.com API. The first edition of the monthly product digest is live now, and so is a deep dive into our Zone Check endpoint.
What's coming
Here's what we're building toward:
More technical depth. We'll continue publishing guides, deep dives, and integration patterns — written by and with the engineers who build the name.com API.
More partner stories. Every partner integration teaches us something about how domain experiences drive business outcomes. We'll keep publishing those stories with the specifics that matter: timelines, team size, metrics, and lessons learned.
Research and perspective. AI-native platforms are shipping domain integrations in days. The platforms winning on conversion are the ones that own the domain step. We'll share research and analysis on where this is heading — grounded in what we're seeing across our partner base.
Come build with us
name.dev is built for the people shipping domain experiences, and we want it shaped by what you actually need. What topics should we cover? What's missing from the docs? What would make your integration easier? Send it directly to ethan@name.com.
We also want to meet you in person. This week you'll find us at Developer Week NYC. Coming up, we'll be at Laracon US in Boston, Future Product Days in Copenhagen, API World in Santa Clara, and vibe coding meetups in Denver. A full events calendar is coming soon.
We're building name.dev for this community. Tell us what you want to see.