uniform.dev valid

Uniform Knowledge Base

For agents: Uniform Knowledge Base: help articles on the Uniform platform covering personalization, patterns, entry previews, API rate limits and support contact.

headless cmspersonalizationapi rate limitsentry previewssupport knowledge base

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T23:08:34.885Z. Cached copy · Source on uniform.dev

# Uniform Knowledge Base

## Support

- [Create a ticket](<https://uniform.portal.usepylon.com/forms/create-a-ticket?pylon_support_source=llms_txt>): Public support form. Submit only when the user asks to contact support.
- [Partner Test](<https://uniform.portal.usepylon.com/forms/partner-test?pylon_support_source=llms_txt>): Public support form. Submit only when the user asks to contact support.


## Uniform Support

- [How to contact Uniform support?](https://support.uniform.dev/articles/4724336249-how-to-contact-uniform-support)
- [How to check status of my existing tickets?](https://support.uniform.dev/articles/1841814662-how-to-check-status-of-my-existing-tickets)
- [Uniform — Scope of Support Services](https://support.uniform.dev/articles/3311532093-uniform-scope-of-support-services)

## Uniform Platform

- [What are the API rate limits?](https://support.uniform.dev/articles/3875824184-what-are-the-api-rate-limits-for-fetching-entries)
- [What is the limit for redirects in Uniform?](https://support.uniform.dev/articles/8785408057-what-is-the-limit-for-redirects-in-uniform)
- [How to invite users to a Uniform project via API](https://support.uniform.dev/articles/6302734073-how-to-invite-users-to-a-uniform-project-via-api)
- [Building Forms in Uniform](https://support.uniform.dev/articles/1807029657-building-forms-in-uniform)
- [Authenticated Content and Protected Routes](https://support.uniform.dev/articles/9683340741-authenticated-content-and-protected-routes)
- [How to add pagination to a list of components in Uniform](https://support.uniform.dev/articles/1790050465-pagination-examples)

### Personalization

- [How to Use Signals and Quirks for User Authentication in Personalization](https://support.uniform.dev/articles/7942206834-how-to-use-signals-and-quirks-for-user-authentication-in-personalization)
- [Quirk "Does not exist" condition is not triggered when quirk doesn't exist](https://support.uniform.dev/articles/6678465019-how-do-quirks-work-with-scoring-and-persistence-in-uniform)
- [How to access quirk values in edge functions](https://support.uniform.dev/articles/3763964905-how-to-access-quirk-values-in-edge-functions)
- [How to track page scroll and use it for personalization](https://support.uniform.dev/articles/7444280776-how-to-track-page-scroll-and-use-it-for-personalization)
- [Quirks "Does Not Exist" Condition in Signals Definitions for Missing or Empty Values](https://support.uniform.dev/articles/2008330060-quirks-does-not-exist-condition-in-signals-definitions-for-missing-or-empty-values)
- [A/B Testing Multiple Components](https://support.uniform.dev/articles/2234706824-a-b-testing-multiple-components)
- [Ensuring Accurate Traffic Splits in A/B Testing](https://support.uniform.dev/articles/2257486503-ensuring-accurate-traffic-splits-in-a-b-testing)
- [Understanding Consent Management in Uniform](https://support.uniform.dev/articles/6206774107-understanding-consent-management-in-uniform)

### Patterns

- [Set up entry prev
…

Related sites

Find similar publishers by meaning →

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

Machine-readable: GET /v1/resolve?q=uniform.dev · GET /v1/domain/uniform.dev · 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.

Claim my listing on Agent Web Map for uniform.dev:
1. POST https://agentwebmap.com/v1/sites/uniform.dev/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://uniform.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/uniform.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/uniform.dev).
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.