Ageniti

Entry Points

@ageniti/core ships a root export plus narrower subpath exports.

Most applications should start with the root package:

import { createAgenitiApp, defineAction, s } from "@ageniti/core";

That keeps usage simple and matches the examples in the documentation.

Available Exports

Root Export

@ageniti/core

Use the root export when you want the main authoring API in one place.

The root export is also where the higher-level packaging and project helpers live, including:

  • buildArtifacts()
  • packageArtifacts()
  • publishArtifacts()
  • initProject()
  • doctorProject()
  • findDefaultAppModule()
  • loadProjectConfig()
  • detectTypeScriptRuntime()

Subpath Exports

@ageniti/core/ai-sdk
@ageniti/core/adapters
@ageniti/core/app
@ageniti/core/cli
@ageniti/core/core
@ageniti/core/dev
@ageniti/core/http
@ageniti/core/json-runner
@ageniti/core/lint
@ageniti/core/manifest
@ageniti/core/mcp
@ageniti/core/react
@ageniti/core/schema

What Each Subpath Contains

  • @ageniti/core/ai-sdk: OpenAI-compatible tools, Responses tools, AI SDK tools, and combined manifests.
  • @ageniti/core/adapters: built-in surface adapters plus adapter helpers.
  • @ageniti/core/app: createAgenitiApp().
  • @ageniti/core/cli: createCli().
  • @ageniti/core/core: runtime and action primitives such as defineAction() and createRuntime().
  • @ageniti/core/dev: createDevServer().
  • @ageniti/core/http: createHttpHandler() and createHttpServer().
  • @ageniti/core/json-runner: createJsonRunner().
  • @ageniti/core/lint: lintActions().
  • @ageniti/core/manifest: manifest helpers such as describeAction(), createSurfaceManifest(), and diffActionManifests().
  • @ageniti/core/mcp: MCP manifest, handler, and stdio server helpers.
  • @ageniti/core/react: createReactActionAdapter().
  • @ageniti/core/schema: s, toJSONSchema(), and SchemaValidationError.

Example Import Patterns

Authoring app actions:

import { defineAction, s } from "@ageniti/core";

Building only an MCP server wrapper:

import { createMcpHandler } from "@ageniti/core/mcp";

Running a validation or tooling step:

import { lintActions } from "@ageniti/core/lint";

Generating AI tool definitions without pulling the app helper:

import { createAISDKTools, createOpenAITools } from "@ageniti/core/ai-sdk";

When To Prefer Subpaths

Prefer a subpath when:

  • you are building a narrowly scoped integration layer
  • you want imports to reflect architectural boundaries
  • you are exposing only one surface from a package or service
  • you are writing tooling around manifests, linting, or schema conversion

Prefer the root export when:

  • you are writing the main application integration
  • you want the shortest onboarding path
  • you do not need explicit module-level separation
  • you need build helpers or project setup helpers that do not have dedicated subpath exports

Type Declarations

All public entry points share the same generated type declarations. The runtime contracts, result envelopes, action metadata, and schema types are consistent across the package exports.

PreviousPackagingNext API Reference