One line in the site. Proof you built it.
Paste an invisible line into your client's site. Once it's live, your portfolio lists the project as confirmed by the site itself, and we check it every week.
Free, every feature. Your profile lives at credited.to/you
01The client's source code.One line from you.
02Your profile.Confirmed by the site.
Marius Serban
credited.to/serban-marius
La Guitarra Flamenca de Yerai Cortés
built it · laguitarraflamencadeyeraicortes.com
Built by Marius Serban. The site itself confirms it, since September 2026.
Looking…ConfirmedNot a mock-up. That site carries that line today. See its receipt →
Real sites, live right now. Each one names its builder in its own code.
7 sites · 2 developers · checked every week
Everything else is a claim.
Nobody gets a line into a site's code without access to the site. So the deploy you already made is the proof.
A screenshotclaim
can be faked in a minute.
A testimonialclaim
needs a client who answers email.
A GitHub graphclaim
proves you commit, not what you shipped.
A line in productionproof
needs nothing but the deploy you already made.
The web forgets who built it.
Ask anyone, even an AI. Unless the site itself says so, nobody can tell who made it.
Ask anyone, even an AI.
Who built bakery-lumiere.fr?
I can’t tell. Only 3 in 100 sites say who made them.
And laguitarraflamenca…
Marius Serban built it. The site itself says so.
Who built bakery-lumiere.fr?
I can’t tell. Nothing on the site says who made it: no “site by”, no studio name, no link in the footer.
Who built laguitarraflamencadeyeraicortes
Marius Serban built it. The site itself says so: it carries Marius’s credited line, checked every week since September 2026.
Confirmed1credited.to/serban-marius
Out of every 100 sites
3 name the person who built them.
34 name only the software they run on.
63 say nothing at all.
bakery-lumiere.fr is made up; the second answer is a real credited page. Rounded, from the 3,236 sites that loaded in a random sample of 5,000, September 2026.Read the study →
A portfolio that builds itself.
Each site you put the line in becomes a row, with a picture of the site and the month it was first confirmed. You never design it.
Marius Serban
Open to freelance work · Spain
5
verified projects
-
01
laguitarraflamencadeyeraicortes.com
La Guitarra Flamenca de Yerai Cortés
built it · confirmed since September 2026
-
02
little.esLittle Spain
built it · confirmed since September 2026
-
03
ferreteriacobsa.esFerretería Cobsa
built it · confirmed since September 2026
Private project
e-commerce · built it · confirmed since September 2026
The first three rows come from a real profile with 5 verified projects, as it reads today.
Under NDA? It still counts.
Mark a project private. Your profile shows a category and the dates, never the client's name or the address. The line itself is a random code only credited can match to you.
Or never open credited at all.
Connect it to your coding agent once. When you finish a site, say so. The agent adds the project, puts the line where your framework wants it, and runs the check after you deploy.
$ claude mcp add --transport http credited https://credited.dev/mcp
- “Credit me for acme.com”create-project
- “Is it verified yet?”check-project
- “What’s on my profile?”list-projects
- “I’m open to work again”set-availability
$ claude
⏺ credited · create-project (name: "Acme", url: "acme.com", role: "built")
⎿ Created "Acme" (id 12) for https://acme.com. A first check is queued; it will fail until the tag is deployed, that is expected.
⏺ Added <meta name="credited" content="cr_…"> to the layout's <head>.
Deploy it and I'll ask credited to check.
⏺ credited · check-project
⎿ Result: tag found via meta tag. Status is now verified (verified since October 2026).
⏺ acme.com is on your profile.
Works with Claude Code, Cursor and any MCP client with OAuth. Setup details · acme.com is an example; the tool names and replies are real.
Every project answers “how do you know?”
Each row on your profile opens a page a client can read in ten seconds, and a developer can check in one command.
La Guitarra Flamenca de Yerai Cortés
Built by Marius Serban. The site itself confirms it, and has since September 2026.
Tag found in production · checked weekly by CreditedBot
How do we know?
Marius added a hidden signature to the site’s code. Only someone with access to the site can do that. Every week, credited checks that it’s still there.
For developers · verify it yourself
$ curl -sL https://www.laguitarraflamencadeyeraicortes.com | grep -io '<meta[^>]*credited[^>]*>'
Prints the tag the site serves right now, the same request CreditedBot makes every week.
What your client might ask.
Short answers you can forward as they are.
Why is there a strange tag in my site?
It’s a verification tag, the same mechanism as Google Search Console. It has no script, loads nothing, and changes nothing for visitors. Send them to the crawler page.
What if the client removes it later?
Your history stays. The profile shows the dates it was live, for example “confirmed January to June 2026”.
Can the line give away who built the site?
No. It’s a random code only credited can match to you. Mark a project private and your profile lists it with the category and the dates, never the URL or the client's name.
Several of us built it.
Each person pastes their own line. It’s a credit like the ones at the end of a film: you were part of the work, not necessarily alone. For an API, or when one file is easier, serve /.well-known/credited.json listing everyone’s code instead.
I work in Laravel, Next, WordPress…
Paste the tag in any layout, or let your coding agent do it through the MCP.
How is this different from a portfolio or LinkedIn?
Those are claims. credited’s proof lives in the client’s own site. See the comparison.
Get credited.
Sign in, add a project, paste one line. Your next site is your next proof.
Free. No card. No project limit.