bkend-databkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, bkend CRUD, bkend column, bkend relation, bkend data
Independent GitHub snapshot · Automated classification · Original documentation governs
name: bkend-data classification: capability classification-reason: Pattern guidance may overlap with model's built-in knowledge as it improves deprecation-risk: medium effort: medium description: | bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, bkend CRUD, bkend column, bkend relation, bkend data user-invocable: false agent: bkit:bkend-expert allowed-tools:
| Type | Description | Example |
|---|---|---|
| String | Text | name, email |
| Number | Numeric | age, price |
| Boolean | True/false | isActive |
| Date | Date/time | birthDate |
| Array | Array | tags: ["a","b"] |
| Object | Nested object | address: {city, zip} |
| Mixed | Any type | metadata |
required: Field must have a valueunique: No duplicate values alloweddefault: Default value when not provided| Field | Type | Description |
|---|---|---|
| id | String | Auto-generated unique ID |
| createdBy | String | Creator user ID |
| createdAt | Date | Creation timestamp |
| updatedAt | Date | Last update timestamp |
Important: bkend uses id (NOT _id) in all API responses.
| Tool | Purpose | Scope |
|---|---|---|
backend_table_create | Create table | table:create |
backend_table_list | List tables | table:read |
backend_table_get | Get table detail + schema | table:read |
backend_table_delete | Delete table | table:delete |
backend_field_manage | Add/modify/delete fields | table:update |
backend_index_manage | Manage indexes | table:update |
backend_schema_version_list | Schema version history | table:read |
backend_schema_version_get | Schema version detail | table:read |
backend_schema_version_apply | Apply schema version (rollback) | table:update |
backend_index_version_list | Index version history | table:read |
backend_index_version_get | Index version detail | table:read |
| Tool | Purpose | Key Parameters |
|---|---|---|
backend_data_list | List records (filter, sort, paginate) | tableId, page?, limit?, sortBy?, sortDirection?, andFilters?, orFilters? |
backend_data_get | Get single record | tableId, recordId |
backend_data_create | Create record | tableId, data: { field: value } |
backend_data_update | Partial update record | tableId, recordId, data: { field: value } |
backend_data_delete | Delete record | tableId, recordId |
All Data CRUD tools require: organizationId, projectId, environmentId (from get_context).
| Operator | Meaning | Example |
|---|---|---|
$eq | Equal | { "status": { "$eq": "active" } } |
$ne | Not equal | { "role": { "$ne": "admin" } } |
$gt / $gte | Greater than / >= | { "age": { "$gt": 18 } } |
$lt / $lte | Less than / <= | { "price": { "$lt": 100 } } |
$in / $nin | In / Not in array | { "tag": { "$in": ["a","b"] } } |
Use search_docs tool to access these guides:
| Doc ID | Content |
|---|---|
4_howto_implement_data_crud | CRUD implementation patterns |
7_code_examples_data | CRUD + file upload code examples |
Use get_operation_schema to get any tool's input/output schema.
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/data/{table} | List (filter, sort, page, limit) |
| POST | /v1/data/{table} | Create |
| GET | /v1/data/{table}/{id} | Get single |
| PATCH | /v1/data/{table}/{id} | Partial update |
| DELETE | /v1/data/{table}/{id} | Delete |
?search=keyword?filter[field1]=value1&filter[field2]=value2$eq, $ne, $gt, $gte, $lt, $lte, $in, $nin?sort=field:asc (or desc)?page=1&limit=20 (default 20, max 100)backend_index_manageFor the latest database documentation, use WebFetch: