How to Embed AI Content Generation in Your Product with the Jity Content SDK

Every SaaS product that touches content creation faces the same build-vs-buy decision eventually. Your users want to generate text, images, and campaign assets inside your platform. You can build that capability yourself — which means managing model integrations, prompt engineering, rate limiting, billing infrastructure, and a maintenance burden that compounds every time a model provider updates their API. Or you can embed a purpose-built content generation layer that already handles all of that.

Jity's Content SDK — available as npm @wityai/jity-api-client — is that layer. It gives your product access to Jity's full content generation stack: text, images, video scripts, and campaign plans, all billable through your Wity Wallet account. Your users get AI content generation inside your product. You do not have to build the infrastructure that powers it.

What You Can Generate

The SDK exposes the full range of Jity's content generation capabilities through a consistent API interface:

• Text content. Blog posts, product descriptions, social media captions, email sequences, video scripts, ad copy. Generation is parameter-driven — you pass the content type, audience, tone, length, and topic; the API returns the content.
• Images. AI-generated visuals including product photography, lifestyle imagery, and ad creatives. If your platform involves product presentation, the image generation endpoint is immediately useful.
• Video scripts. Structured scripts for short-form video, long-form YouTube content, and advertising. Format-aware — a YouTube Shorts script is structured differently than a 10-minute tutorial script.
• Campaign plans. Full content calendars with post-by-post breakdowns, platform-specific formatting, and scheduling recommendations.

Installation and Basic Usage

Getting started is a standard npm install:

npm install @wityai/jity-api-client

Authentication uses your Wity Wallet API key. A basic text generation call in TypeScript looks like this:

import { JityClient } from '@wityai/jity-api-client';

const client = new JityClient({ apiKey: process.env.WITY_API_KEY });

const result = await client.content.generate({
  type: 'product-description',
  inputs: {
    productName: 'Hydrating Face Serum',
    keyBenefits: ['hyaluronic acid', 'lightweight', 'fast-absorbing'],
    audience: 'skincare-aware women 25-40',
    tone: 'clean, clinical, confident',
    length: 'medium'
  }
});

console.log(result.content);

The response includes the generated content, token usage for billing reconciliation, and metadata about the generation parameters. Image generation follows the same pattern with image-specific parameters — style, dimensions, subject description — and returns a URL to the generated asset.

Billing: Usage Flows Through Your Wity Wallet

The billing model is designed for products where AI generation is a feature your users consume, not just an internal tool. When your users trigger content generation through your platform, the usage charges flow through your Wity Wallet account. You control how you present that cost to your users — as a consumed credit, a usage-based line item, or absorbed into your subscription pricing. The SDK gives you the usage data you need to build whichever billing model fits your product.

This is significantly cleaner than managing direct API relationships with multiple AI providers, each with their own billing accounts, rate limits, and pricing structures. One account, one wallet, one usage report covering all generation activity across your product.

Use Cases Worth Building

The SDK opens up a category of product features that were previously too expensive or complex to build internally. Four use cases stand out as high-value and immediately buildable.

A CMS with first-draft generation. Your users are already writing in your CMS. Adding a "Generate first draft" button — powered by the Jity API — turns a blank-page problem into an editing problem. The user provides the topic and parameters; the API returns a structured draft. Time to first word: seconds instead of hours.

A Shopify app that writes product descriptions. Product description quality directly affects conversion rates, and most merchants have hundreds or thousands of SKUs with mediocre descriptions. An app that takes product attributes and generates optimized, on-brand descriptions at scale is immediately useful and repeatable across every merchant's catalog.

An e-commerce platform that generates social posts for merchants. Merchants on your platform want to promote their products on social media but do not have the time or skill to produce platform-native content. A feature that takes a product listing and generates Instagram captions, LinkedIn posts, and Twitter copy removes a significant friction point from their marketing workflow.

An internal reporting tool that generates weekly summaries. If your product collects data that teams review regularly, the gap between "data available" and "insight communicated" is often a writing task. The API can take structured data inputs and generate narrative summaries — weekly performance reports, customer health summaries, financial snapshots — automatically on a schedule.

The Compounding Benefit

The strategic case for embedding Jity's SDK rather than building your own content AI layer is not just the immediate development time saved. It is the ongoing maintenance delta.

Building your own integration means owning the model selection decisions, the prompt engineering, the failure handling, the rate limit management, and the infrastructure updates every time an upstream provider changes their API. That is a non-trivial engineering burden that compounds over time and competes with product feature development for engineering attention.

The SDK keeps that burden external. When Jity updates its models or improves its generation quality, your product benefits automatically. When a model provider changes their API, Jity handles the adaptation. Your engineering team stays focused on the product problems only you can solve.

The SDK is available now at npm as @wityai/jity-api-client. If your product touches content creation in any form, the integration time is measured in hours, and the feature value compounds from the first generation.