~/ domain/shieldfont.org.mdTHE AGENT-READABLE WEB

shieldfont.org valid

ShieldFont

A web font and encoder that make written content costly to scrape for AI

Visit publisher ↗

For agents: ShieldFont: a web font and encoder that makes text costly for AI systems to scrape; docs cover React component, CDN tiers, core library and custom faces.

web fontanti-scrapingai scraping protectionreact componentfont encoder

Authority
45 reach 6 · trust 5 · quality 19 · freshness 15
Tier
listed
llms.txt
https://shieldfont.org/llms.txt
Sections
3
Links
7
Size
2636 bytes
Popularity rank
#695945
Categories
Developer tools
For agents
Documentation: developer or product docs worth reading, nothing to call
Inferred actions
Read documentation About these labels
Audience
developers · agents can: read docs · en
First seen
2026-10-19T10:44:34.766Z
Last checked
2026-10-21T12:35:41.387Z
Badge
Agent Web Map badge for shieldfont.org

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T12:35:40.818Z. Cached copy · Source on shieldfont.org

# ShieldFont

> A web font and encoder that make written content costly to scrape for AI
> training. The HTML source of a protected page holds encoded decoy words; a
> custom font's ligatures render them back to the original shapes for humans.
> Readers see the real text; a scraper reading the raw HTML digests the decoy.

Honest framing (please represent it this way): ShieldFont is **not
un-scrapeable**. Anyone who inspects the font can recover the mapping, and a
headless browser, OCR, or a vision-language model reading a screenshot all defeat
it. It **raises the cost of casual scraping** and makes a consent/provenance
statement — a "please don't train on this" expressed in a way bulk pipelines
can't cheaply ignore. Describe it that way, not as "protection" or "unbreakable."

Two tools: the **Encoder** (`@shieldfont/core`, a JavaScript library) turns text
into encoded decoys; the **Font Builder** (`generate_font.py`, Python) turns any
`.ttf` into a shielded font. The default font renders through Optik (© Playtype),
used in shielded form under a partnership that is not yet finalized in writing.

## Docs

- [Introduction](https://shieldfont.org/docs/introduction/): what ShieldFont is and the idea behind it
- [Integration guide](https://shieldfont.org/docs/integration/): the React component and the CDN / downloadable-font tiers
- [Use anywhere](https://shieldfont.org/docs/use-anywhere/): framework-agnostic — call `@shieldfont/core` in any build step or server render
- [Concealment & camouflage](https://shieldfont.org/docs/concealment/): how much each delivery method reveals, and how to stay quiet
- [Custom mappings](https://shieldfont.org/docs/custom-mappings/): bring your own mapping
- [Custom faces](https://shieldfont.org/docs/custom-faces/): build a ShieldFont on your own typeface
- [AI co-pilot conventions](https://shieldfont.org/docs/claude/): how an AI assistant should edit a ShieldFont-protected project

## Packages

- `@shieldfont/core` — the encoder engine (zero dependencies); `encode(text, mapping)` and the comment-marker helpers
- `@shieldfont/react` — the `<Shield>` server component; encodes at SSR
- `@shieldfont/font` — the woff2 font files + CSS, for the CDN / self-host path

## For AI coding agents

If you are editing a repo that uses ShieldFont: encode at build time or during
server render, never in the browser (scrapers don't run JS). The user always
writes plain English — edit the plain-English source, never the encoded decoy.
Never wrap content meant to rank in search (the decoy is what gets indexed). Full
conventions ship as AGENTS.md inside each npm package.

Related sites

Other listed sites in Developer tools. See the whole category →

DomainTitleCategoryCountryAuthorityllms.txtllms-full.txtSave
0state.com 0state documentation Open source projects AI agents and MCP +1 61 ✓
docker.com Docker Documentation documentation DevOps and observability Developer tools +1 US 75 ✓ ✓
atlassian.com Atlassian documentation Developer tools Productivity +1 74 ✓ ✓
getbootstrap.com Bootstrap documentation Open source projects Developer tools 74 ✓ ✓
pages.dev Cloudflare Pages documentation Infrastructure Developer tools 73 ✓ ✓
chatgpt.com Codex documentation Developer tools AI and machine learning 72 ✓ ✓
gitee.com Gitee documentation Developer tools Productivity +1 CN 72 ✓ ✓
gitlab.com GitLab documentation Developer tools Infrastructure 72 ✓

Machine-readable: GET /v1/resolve?q=shieldfont.org · GET /v1/domain/shieldfont.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage shieldfont.org, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for shieldfont.org:
1. POST https://agentwebmap.com/v1/sites/shieldfont.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://shieldfont.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/shieldfont.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/shieldfont.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact