Put Catholic AI inside your own app.
Your product, your brand, your users. Synderesis supplies the AI underneath: an open-weight model retrained to align with Catholic values, which can return the official Church sources behind its answers.
Start today with a self-serve API key. Become a white-label partner when your product needs agreed rates, capacity and branding.
You bring the app. We bring the AI.
Picture a Catholic education app with twenty thousand users. Training its own AI model would be slow and expensive. Relying only on a general-purpose model would leave its Catholic purpose to a prompt.
Instead, it connects to Synderesis through the API. One model can sit underneath many Catholic products, each under its own name.
The product people use
Its name, design, accounts, features and pricing — and the relationship with its users.
The AI underneath
The retrained model, answers that can cite official Church sources, and the infrastructure that runs them.
Catholic by training, not by prompt.
A general-purpose model with a Catholic prompt keeps its own defaults underneath. Synderesis starts from a model retrained to align with Catholic values.
Values in the model
Catholic values are part of how the model was retrained, so your app does not have to hold them together with a long prompt.
Answers your users can check
The answers endpoint can return the official Church sources behind an answer, so your interface can show where it comes from.
Conversations stay out of training
Synderesis never uses your users' prompts or answers to train its model. The API keeps no conversation history.
Start self-serve. Grow into a partnership.
Both paths use the same model and the same API. What changes is the agreement around it.
For prototypes and first releases
Create an account, make a key and call the API from your backend today.
- Answers with official Church sources, plus OpenAI-style chat completions with function calling
- Spark, Pro or automatic model routing
- Several keys per account, each with its own prefix for tracking
- Paid through your account's subscription and credit
For products with a real user base
A written agreement for companies that put Synderesis in front of their own users.
- Only your brand, or “Powered by Synderesis” — your choice
- Rates and capacity agreed for your number of users
- Separate keys for each product or environment
- Processing terms in writing, and onboarding help from our team
Your server talks to Synderesis. Your users talk to you.
The API key stays on your server, so your app stays in charge of accounts, limits and what users see.
- Your usersUse your app, under your brand
- Your appScreens, accounts and features
- Your serverHolds the API key and sets limits per user
- Synderesis APIThe model, Church sources and the answer
The answer, with its sources when present, comes back the same way.
- Create a Synderesis account, then an API key on the Account page.
- Call the answers or chat endpoint from your server — never from a browser or a mobile app bundle.
- Show the answer, and its sources when present, in your own interface.
curl --fail-with-body https://www.synderesis.eu/v1/answers \
-H "Authorization: Bearer $SYNDERESIS_API_KEY" \
-H "Content-Type: application/json" \
--data '{"model":"spark","question":"Explain human dignity in two sentences.","grounding":true,"max_tokens":1024}'
Made for Catholic products.
Examples of what partners can build. Each keeps its own name and design.
Education and catechesis apps
Course companions for OCIA, confirmation classes and homeschooling families, with answers that can point back to Church teaching.
Parish and diocesan software
An assistant inside parish management, giving or communication tools, so staff get help without leaving the system they already use.
Publishers and prayer apps
A question-and-answer companion beside your books, courses or daily readings, inside your own app.
Also a fit for learning platforms used by Catholic schools and universities, and for agencies that build software for Catholic organisations.
Settled in writing before you launch.
The self-serve API comes without a service commitment. A partnership puts the terms a product with many users needs into writing.
Rates and capacity
Prices and throughput agreed for your expected number of users.
Branding
Only your brand, or “Powered by Synderesis”. Neither may suggest approval by the Church.
Data processing
Processing terms, model providers and processing locations set out for your deployment.
Onboarding and support
Help from our team with integration, testing and launch.
What builders ask.
Can our app use its own name?
Yes. Under a partner agreement your app can show only your brand, or “Powered by Synderesis” if you prefer.
Are our users' conversations used for training?
No. Synderesis never uses your users' prompts or answers to train its model, and the API keeps no conversation history.
Can we call the API from a browser or a mobile app?
Not directly. Call it from your own server and keep the key there. Browser cross-origin requests are not enabled.
Does it work with the OpenAI SDK?
Partly. The chat endpoint follows the OpenAI Chat Completions format, so selected SDK calls work with a custom base URL. Other SDK features are not supported.
Do answers stream word by word?
No. Answers arrive complete, after checks. The chat tool path can deliver the finished answer as server-sent events.
Where is data processed?
Synderesis is an EU company. The model providers and processing locations for your deployment are set out in your partner agreement. Private-cloud and on-premise options are part of the Synderesis Platform.
What does it cost?
Creating an account is free. Ongoing API use is paid through your account's subscription and credit. Partner rates are agreed in writing.
Can we say our app is approved by the Church?
No. Synderesis is independent and is not endorsed by the Catholic Church or the Holy See, and partner apps must not suggest otherwise.
Tell us what you're building.
Share your product, your number of users and your timeline. We will reply with how a partnership could work.