oxedyne/daimond — www/guide/models.html

7.2 KiB, 1 run

created by r2519314175:1271, which is this file's identity for as long as the history lasts, whatever it is later renamed to

download · who wrote it · its history

1	<!DOCTYPE html>
2	<html lang="en" data-guide-locale="en" data-guide-locales="en de es fr ja ko pt-BR zh-Hans">
3	<head>
4	<meta charset="UTF-8">
5	<meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover">
6	<title>Models & credits — Daimond guide</title>
7	<link rel="icon" type="image/svg+xml" href="../assets/daimond_mark.svg">
8	<link rel="stylesheet" href="../css/variables.css">
9	<link rel="stylesheet" href="../css/guide.css">
10	<script src="frame.js"></script>
11	<script src="search-index.js"></script>
12	<script src="search.js"></script>
13	</head>
14	<body>
15
16	<header class="site-head">
17	<div class="site-head-inner">
18	<a class="brand" href="index.html" aria-label="Daimond guide, home">
19	<img class="wordmark wm-dark" src="../assets/daimond_word.svg" alt="Daimond" translate="no">
20	<img class="wordmark wm-light" src="../assets/daimond_word_dark.svg" alt="Daimond" translate="no">
21	<span class="brand-sub">Guide</span>
22	</a>
23	<nav class="site-nav" aria-label="Guide pages">
24	<a href="index.html">Getting started</a>
25	<a href="interface.html">The interface</a>
26	<a href="models.html" aria-current="page">Models & credits</a>
27	<a href="chats-and-diamonds.html">Chats & Diamonds</a>
28	<a href="capps.html">Capps</a>
29	<a href="email-web-files.html">Email, Web & files</a>
30	<a href="accounts.html">Accounts</a>
31	<a href="sync.html">Cross-device sync</a>
32	<a href="spending.html">Spending</a>
33	<a href="machine-operations.html">Machine Operations</a>
34	<a href="social.html">Social</a>
35	</nav>
36	</div>
37	</header>
38
39	<main>
40	<h1>Models & credits</h1>
41	<p class="lede">A daimon thinks with a model. You can bring your own provider key and pay that provider directly, or buy credits and let Daimond run a model for you. This page covers both, and how to keep credits topped up.</p>
42
43	<h2 id="s1">Two ways to power a daimon</h2>
44	<div class="cards">
45	<div class="card">
46	<h3 id="s2">Bring your own key</h3>
47	<p>Connect an account you already hold with a model provider. Your messages go straight to that provider; Daimond is not in the path, and nothing is charged by us.</p>
48	</div>
49	<div class="card">
50	<h3 id="s3">Buy credits</h3>
51	<p>No provider account to manage. Daimond runs the model for you and draws down the credits you bought. No subscription: you keep what you buy.</p>
52	</div>
53	</div>
54	<p>Either is enough to start. You can do both: connect a key for everyday work and keep credits for when you would rather not manage one.</p>
55
56	<h2 id="s4">Connecting a provider</h2>
57	<p>Open the <span class="ui">Models</span> row in the admin panel, bottom-left. It lists a key for each provider you use and which model new chats start on. To add one, choose <span class="ui">+ Add provider</span> and answer the same three questions, whoever the provider is.</p>
58
59	<figure class="shot" data-shot="models-form">
60	<img alt="The Add provider form: a provider drop-down, an API key box, and a default model drop-down, with a Save and start button." src="shots/models-form.png" loading="lazy">
61	<figcaption>Adding a provider: choose the provider, paste the key, star a default model, then Save & start.</figcaption>
62	</figure>
63
64	<ol class="steps">
65	<li>
66	<h3 id="s5">Choose a provider</h3>
67	<p>Pick from the list: <strong translate="no">Anthropic</strong>, <strong translate="no">Fireworks AI</strong>, <strong translate="no">OpenRouter</strong>, <strong translate="no">Together AI</strong>, <strong translate="no">Groq</strong>, <strong translate="no">DeepInfra</strong>, or <strong>Custom</strong> for any other service speaking the same chat-completions API. Choosing Custom reveals a <strong>Base URL</strong> box to point Daimond at that service.</p>
68	</li>
69	<li>
70	<h3 id="s6">Paste your API key</h3>
71	<p>Paste the key from your provider account into the <strong>API key</strong> box. It is stored on this device only, wrapped under your passphrase, and sent only to the provider you chose.</p>
72	</li>
73	<li>
74	<h3 id="s7">Star a default model</h3>
75	<p>Choose a <strong>Default model</strong> from the list (or type a model id for a custom provider). This is the one model new chats and Diamonds start on. Then choose <span class="ui">Save & start</span>.</p>
76	</li>
77	</ol>
78
79	<div class="note"><strong>Everything stays on this device.</strong> Your keys, chats and files live only in this browser. Nothing is sent to us: a provider key you add talks to that provider, and to no one else.</div>
80
81	<h3 id="s8">The default model, and picking another for one chat</h3>
82	<p>One model is the default that new chats and Diamonds begin on. Any connected model can be chosen for a single chat, from the selector in its header at the top-right of the centre panel; the default is untouched. A Diamond can also be given a separate model for the workers it dispatches.</p>
83
84	<h2 id="s9">Buying credits</h2>
85	<p>Open the <span class="ui">Credits</span> row in the admin panel. It shows your balance and a set of packs to buy. There is no subscription: you keep what you buy, and nothing is charged again unless you turn on auto-reload.</p>
86
87	<figure class="shot" data-shot="credits">
88	<img alt="The Credits view: the current balance, a row of credit packs to buy, and the auto-reload settings below." src="shots/credits.png" loading="lazy">
89	<figcaption>Credits: your balance, packs to buy, and the auto-reload settings underneath.</figcaption>
90	</figure>
91
92	<p>Payment is handled on the payment provider's own hosted page. No card number, expiry or security code is ever typed into Daimond, so there is nothing here to leak.</p>
93
94	<h2 id="s10">Auto-reload</h2>
95	<p>Auto-reload is a standing instruction to buy credits when they run low, so a long job does not stop halfway. It is the one place Daimond may charge a saved card while you are away, and so is deliberately explicit. Three numbers set it, below the packs in the Credits view:</p>
96	<ul>
97	<li><strong>Below</strong>: the balance at which a top-up fires.</li>
98	<li><strong>Buy</strong>: how much one top-up adds.</li>
99	<li><strong>Never more than</strong>: a hard cap on total top-ups in a calendar month. Set this one carefully. It is a ceiling rather than a target, and it is enforced on the same code path as the charge, so nothing can walk around it.</li>
100	</ul>
101
102	<div class="note">Auto-reload cannot be switched on without a saved card. A control that turned on and then silently failed would be worse than one that is disabled and says why. Saving a card is a redirect to the payment provider's hosted page; Daimond never sees the card details.</div>
103
104	<div class="next">
105	<a href="interface.html">← The interface</a>
106	<a href="chats-and-diamonds.html">Next: Chats & Diamonds →</a>
107	</div>
108	</main>
109
110	<footer class="site-foot">
111	<span>Daimond runs in your browser. Nothing here is sent to us.</span>
112	<nav aria-label="Guide pages">
113	<a href="index.html">Getting started</a>
114	<a href="interface.html">Interface</a>
115	<a href="models.html">Models</a>
116	<a href="chats-and-diamonds.html">Chats & Diamonds</a>
117	<a href="capps.html">Capps</a>
118	<a href="email-web-files.html">Email, Web & files</a>
119	<a href="accounts.html">Accounts</a>
120	<a href="sync.html">Cross-device sync</a>
121	<a href="spending.html">Spending</a>
122	<a href="machine-operations.html">Machine Operations</a>
123	<a href="social.html">Social</a>
124	</nav>
125	</footer>
126	</body>
127	</html>