@smartfront/server
v0.2.2
Published
Smartfront server operations SDK
Readme
@smartfront/server
Completed, validated router decisions bypass the extraction LLM. Unresolved parameters go through model interpretation first so supplied text, numbers and references can be extracted automatically. A confidently identified single operation produces pending.form only when interpretation still needs user input. Explicit custom-router form selections also bypass interpretation. Direct execution and form responses are marked local; model-extracted actions retain result follow-ups. Typed parameter form behavior.
Separate Jev/LLM routing and deterministic operation validation for Node and Fetch runtimes. Provider secrets stay server-side. The backend proposes operations; browser handlers execute them.
Set autoParameterForms: false in server options to collect unresolved parameters through model follow-up questions for all clients. Clients can also disable forms per configuration with the same flag. Either value of false takes precedence over explicit router form selections; fully resolved direct execution remains available. The default is true.
import { createFetchHandler } from '@smartfront/server';
export const POST = createFetchHandler({ apiKey: process.env.OPENROUTER_API_KEY!, allowNoGuard: false });import { createNodeHandler } from '@smartfront/server';
app.post('/v1/chat', createNodeHandler({ apiKey: process.env.OPENROUTER_API_KEY! }, {
authenticate: (request) => verifySession(request.headers.get('authorization')),
rateLimit: (identity) => quotaStore.allow(identity!.tenantId, identity!.userId),
}));verifySession must return verified { tenantId, userId } or reject. A publishable key is public project identification, not authentication. resolveServer(identity) supports tenant-owned credentials/configuration on each request. Requests use protocol version 1, byte limits and abort signals; errors use { error: { code, message } }. Keep debug off in production because diagnostic responses include context/prompts. Never trust browser schemas as server-side permissions.
The repository includes a standalone Docker/Node deployment under apps/server. Workspace build/test: npm run build -w @smartfront/server, npm run test -w @smartfront/server after building core.
