# Turn a title into a URL slug from an AI agent

You need to turn a title or a label into a URL-friendly slug, with the same result every time.

Use `text-slugify@1.0.0`. It is free and needs no key or sign-up. Create a deterministic ASCII or Unicode slug using an explicit, documented normalization profile.

## Why call a tool for this

Slug rules differ on accents, punctuation and non-Latin scripts. Here the profile is part of the call, so the rule used is visible and repeatable.

## Call it over HTTP

```sh
curl -X POST https://computefirst.net/v1/tools/text-slugify/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"text":"Crème brûlée","profile":"ascii"}'
```

Response:

```json
{
  "result": {
    "slug": "creme-brulee"
  }
}
```

## Call it over MCP

Connect `https://computefirst.net/mcp` ([setup](/docs#connect)), then call `execute` with:

```json
{
  "id": "text-slugify",
  "version": "1.0.0",
  "input": {
    "text": "Crème brûlée",
    "profile": "ascii"
  }
}
```

## Check the result

Choose a profile. ascii removes accents and drops every other non-ASCII character, so a title with no Latin letters or digits gives an empty slug; check for that. unicode keeps letters, numbers and their combining marks in every script. Input is limited to 4096 UTF-8 bytes, and a slug that normalization makes longer than 4096 characters is rejected. To check a name you already have, use url-safe-name-check instead.

Full contract, limits and unsupported cases: [Text slugify](/tools/text-slugify).

## Related tools

- [URL safe name check](/tools/url-safe-name-check)
- [Github heading slug](/tools/github-heading-slug)