Services

It is reasonable to have an API endpoint that doesn’t quite fit into a Model’s namespace, or that needs to interact with multiple Models and Data Sources.

For these cases, Cloesce supports data-less models, called a service. Models with no columns, no KV/R2 properties, no key fields, and no D1 binding are considered services, essentially a namespace for static API methods.

Defining a Service

A service is a model block with empty braces:

model FooService {}

api FooService {
    get do_foo() -> string
}

The implementation is the same as for any other model:

import * as clo from "@cloesce/backend.js";

const FooService = clo.FooService.impl({
  do_foo() {
    return "foo";
  },
});

Constraints

A Service:

• Can declare only static API methods
• Cannot declare a data source
• Has no generated Self, Key, Source, or Orm namespace.
• Cannot be used as a type in fields or API parameters/returns

Adding any data field (column, KV, R2, key field) makes it a regular model with the full set of generated helpers.