Integrations

Language detection and translation

Pick the language services your server uses.

• Detect languages with the built-in detector or set up DeepL for it.
• Turn on DeepL translation with your own credentials for the service.
• If no provider is set up, the server can turn translation off.

Translation only works when a service is set up and turned on.

AI providers and models

Pick AI providers and choose which models your server offers.

• Manage provider credentials and look through the model catalog.
• Welley supports OpenAI, Anthropic, Google and OpenRouter as providers.
• A model's capabilities decide which jobs it can do.

AI services need credentials from the operator, a model that's turned on and a provider that's available.

See all screens

AI tools and limits

Choose which AI tools people can use.

• Set the models and daily limits for supported text and image tools.
• Your server's configuration decides which AI options are available.
• Personal and group actions still follow their own permissions.

Which tools work depends on how providers are set up and what the models support.

See all screens

AI bots

Make a bot with its own profile, model, instructions and permissions you control.

• Choose activity, content, question or scheduled triggers.
• Choose what the bot is allowed to do.
• Try the bot out in its editor before you publish it.

The operator has to set up a model that supports the tools the bot needs. A bot can only do what it has explicit permission to do.

MCP servers

Let AI bots use the external tools you pick.

• Set up Model Context Protocol servers in the Integrations section.
• Start from an available preset or set up a custom service.
• Turn the service on only for the scopes that need it.

External tools need a configured service and any credentials it requires.

AI search setup

Pick and look after the model behind semantic search.

• Choose an embedding model and check whether AI search is on.
• When the embedding configuration changes, follow the recalculation as it runs.
• The screen tells apart active, unconfigured and failed recalculation states.

AI search needs an embedding model that's turned on, and the index has to be recalculated.

Webhooks

Connect server events to external services.

• Create webhook integrations and choose which events they subscribe to.
• Use signed HTTP delivery with retries, or a pull subscription with its own secret.
• Managing server webhooks needs its own permission.

Whether delivery works depends on the service on the other end.

FASP providers

Connect a Fediverse Auxiliary Service Provider to get shared search capabilities.

• Register one or more providers and see their registration state and capabilities.
• Choose a default provider for each supported capability.
• Only accepted providers with the capability turned on can be a default.

What search finds depends on your connected providers, public content and federation policy.

Link preview service

Set up a separate service for web link previews.

• Set the preview service endpoint on the FASP integration page.
• Clearing the endpoint turns this service off.
• How a preview turns out depends on the website and the service.

FASP remote administration

Manage a connected FASP service from the Welley admin panel.

• See registrations, subscriptions and backfill tasks.
• Manage the service's block list and relay connections.
• The overview and settings tabs show provider operations.

Remote administration needs a configured FASP admin connection. It's separate from your server's own ActivityPub relay list.