01
Direct
One call in. One image out.
Show the shortest path from a URL to a finished screenshot. Let the product prove the point.
Brand guidelines
The Grabbit brand.
Fast, exact, and built to be called. This is the visual and verbal system behind the agent-first screenshot API.
brand/grabbit
#155BFF
#6D35F5
#06142D
#13C8A3
01Principles
The result carries the brand.
Grabbit removes the browser work between a URL and a finished image. The brand should feel just as direct: crisp hierarchy, visible proof, and no ceremony around a simple call.
02
Exact
The pixels are the proof.
Use real captures, real dimensions, and real response data. Precision beats adjectives.
03
Agent-first
Built to be called, not babysat.
Speak to developers and agents as capable operators. Keep setup short and outputs structured.
02Logo
The rabbit in the frame.
The rabbit sits inside a crop frame. The ears make it recognizable at small sizes, while the frame ties the mark to capture and composition. The blue-to-violet gradient adds speed without turning the interface into a light show.
Light surface lockup
Dark surface lockup
Light lockup
Light surfaces
Dark lockup
Dark surfaces
Gradient mark
Avatars and social profiles
Blue mark
Light UI at small sizes
White mark
Dark UI at small sizes
Usage rules
Keep the mark quick and recognizable. Give it room, then leave it alone.
- Use the full lockup when the audience may not know Grabbit yet.
- Use the mark alone for avatars, favicons, and compact product chrome.
- Keep clear space equal to one rabbit eye around the mark.
- Do not recolor, rotate, outline, stretch, or add effects to the assets.
- Use the dark lockup on dark surfaces and the light lockup everywhere else.
03Color
Electric blue. Vivid violet. Deep navy.
Blue carries the action. Violet adds energy at the edge. Navy keeps the system grounded, and green confirms that the capture landed. Product code uses semantic tokens so both modes keep the same hierarchy.
Identity palette
Electric Blue
#155BFFbrandConfig.colors.primary
Vivid Violet
#6D35F5brandConfig.colors.accent
Deep Navy
#06142DbrandConfig.colors.navy
Capture Green
#13C8A3brandConfig.colors.success
Light mode
color-scheme: lightCanvas
#FBFCFE--color-background
Surface
#F4F7FB--color-card
Muted surface
#EAEFF5--color-muted
Ink
#0B121D--color-foreground
Secondary ink
#545B66--color-muted-foreground
Hairline
#D6DBE3--color-border
Dark mode
color-scheme: darkCanvas
#090D15--color-background
Surface
#111620--color-card
Muted surface
#191F2B--color-muted
Ink
#F2F5FB--color-foreground
Secondary ink
#A4ABB6--color-muted-foreground
Hairline
#282E39--color-border
04Typography
Manrope leads. Geist works. Mono proves.
Headlines stay compact and decisive. Body copy gets out of the way. Code and response data use monospace because the product is an API and the details matter.
500, 600, 700
Capture the page. Keep the proof.
Manrope
Headlines
font-headline400, 500, 600
Send a URL and get a hosted image back.
Geist
Body and interface
font-sans400, 500, 600
POST /api/v1/grabs
Geist Mono
Code and data
font-monoAny URL. One call.
Pixel-perfect screenshot.
Capture full pages, fixed viewports, or one element. Get back a hosted PNG, JPEG, or WebP with the dimensions and timing attached.
$ grabbit https://example.com
05Image direction
Show the capture, not a promise of one.
The product makes images. Brand imagery should come from that capability. Use real captures as evidence, frame them with restraint, and keep every source page recognizable.
stripe.com
WebP · 1280 × 800Example capture
Captures are evidence.
- Use screenshots made by Grabbit whenever the product can supply the image.
- Keep the captured page legible. Crop with intent, never as decoration.
- Preserve the source URL or domain when provenance helps the story.
- Use the blue-to-violet aura behind screenshots, never over the captured pixels.
- Prefer interface evidence over stock photography and abstract 3D art.
06Voice
Fast, exact, and calm.
Fast, exact, and calm. Grabbit sounds like the developer who already reduced the problem to one clean API call.
How we write
- Lead with the result, then show the request.
- Use concrete inputs, outputs, prices, dimensions, and response times.
- Keep sentences short enough to scan beside code.
- Say screenshot, capture, URL, request, image, key, and credit consistently.
- Write to developers and agents as capable operators.
Lines that sound like Grabbit
Send a URL. Get a screenshot.
One POST. Pixel-perfect output.
No browser fleet to run.
Built for developers. Ready for agents.
Avoid
Hype without a number or example.
Claims such as effortless, magical, revolutionary, or category-defining.
Calling a capture a render when screenshot is clearer.
Inventing a second name for an API key, grab, credit, or webhook.
07Files for agents
The same brand, in three readable formats.
Use the visual page for people, Markdown for context windows, JSON for tooling, and plain text for terminals. Each file comes from the same brand source.
brand.md
The full reference with tables, usage rules, voice, and downloadable assets.
Read Markdown
brand.json
Structured identity, color, typography, voice, logo, and image-direction data.
Open JSON
brand.txt
A compact plain-text reference that pastes cleanly into any prompt or terminal.
Open text
$ curl https://www.grabbit.live/brand.mdAgent-ready MarkdownReady to capture something?
Get a free test key and make the first request.