cleverbrush.com valid
Cleverbrush Framework
Schema-first TypeScript libraries for validation, HTTP APIs, typed clients,
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T15:06:14.252Z. Cached copy · Source on cleverbrush.com
# Cleverbrush Framework
> Schema-first TypeScript libraries for validation, HTTP APIs, typed clients,
> database access, forms and object mapping. Libraries compose without codegen.
Start with schemas, share a browser-safe API contract, implement its handlers on
the server, then create a client from that same contract. Database schemas and
public response schemas can differ; select and map fields explicitly.
## Package map
| Area | Package | Documentation |
| --- | --- | --- |
| Validation and extensions | `@cleverbrush/schema` | [Schema](https://schema.cleverbrush.com) |
| JSON Schema conversion | `@cleverbrush/schema-json` | [README](https://github.com/cleverbrush/framework/tree/development/libs/schema-json) |
| HTTP contracts and handlers | `@cleverbrush/server` | [Server](/server) |
| HTTP clients and React hooks | `@cleverbrush/client` | [Client](/client/getting-started) |
| API specifications | `@cleverbrush/server-openapi` | [OpenAPI / AsyncAPI](/server-openapi) |
| Authentication and authorization | `@cleverbrush/auth` | [Auth](/auth) |
| Dependency injection | `@cleverbrush/di` | [DI](/di) |
| Environment configuration | `@cleverbrush/env` | [Env](/env) |
| SQL queries and schema metadata | `@cleverbrush/knex-schema` | [Queries](/knex-schema) |
| Entities, relations and tracking | `@cleverbrush/orm` | [ORM](/orm) |
| Database migrations | `@cleverbrush/orm-cli` | [README](https://github.com/cleverbrush/framework/tree/development/libs/orm-cli) |
| Object transformations | `@cleverbrush/mapper` | [Mapper](/mapper) |
| Schema-driven React forms | `@cleverbrush/react-form` | [Forms](/react-form) |
| Worker-thread jobs | `@cleverbrush/scheduler` | [Scheduler](/scheduler) |
## Core workflow
This small example uses an in-memory collection, not persistent storage. Keep
`contracts.ts` shared; do not import server implementations into browser bundles.
### 1. Define schemas and the shared contract
```typescript
// contracts.ts
import { defineApi, endpoint } from '@cleverbrush/server/contract';
import { array, boolean, number, object, string } from '@cleverbrush/schema';
export const Todo = object({
id: number(),
title: string(),
completed: boolean()
});
const CreateTodo = object({ title: string().minLength(1).maxLength(200) });
export const api = defineApi({
todos: {
list: endpoint.get('/api/todos').responses({ 200: array(Todo) }),
create: endpoint.post('/api/todos')
.body(CreateTodo).responses({ 201: Todo })
}
});
```
### 2. Implement the handlers
```typescript
// todos.ts
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| valibot.dev | Valibot | documentation Developer tools Documentation and reference | — | 56 | ✓ | ✓ | |
| quicktype.io | quicktype | interface AI and machine learning Developer tools +1 | US | 53 | ✓ | ✓ | |
| drizzle.team | Drizzle | documentation Data and analytics Infrastructure +2 | — | 62 | ✓ | ✓ | |
| tanstack.com | TanStack | documentation Developer tools APIs and SDKs | — | 65 | ✓ | ✓ | |
| appwrite.io | Appwrite | documentation Developer tools AI agents and MCP +1 | — | 58 | ✓ | ✓ | |
| mcp-use.com | mcp-use | documentation AI agents and MCP Developer tools | — | 53 | ✓ | ✓ | |
| flowgram.ai | FlowGram.AI | documentation AI and machine learning Developer tools | — | 48 | ✓ | ✓ | |
| webflow.com | Webflow Developer Documentation | interface Developer tools APIs and SDKs | US | 71 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=cleverbrush.com · GET /v1/domain/cleverbrush.com · 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 cleverbrush.com, 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.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- 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.
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 cleverbrush.com:
1. POST https://agentwebmap.com/v1/sites/cleverbrush.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://cleverbrush.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/cleverbrush.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/cleverbrush.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.