[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"content:about":3},{"body":4,"toc":5},"\u003Ch1>About cronservices\u003C\u002Fh1>\n\u003Cp>Most scheduled code is plumbing. Call an API, pick a few fields out of the response, send them somewhere else. Yet each piece of it usually becomes a function, which then needs a repo, a deploy target, a cron trigger, secrets, logs, and someone to notice when it stops running.\u003C\u002Fp>\n\u003Cp>cronservices turns that plumbing into configuration. A job is a cron expression and a short pipeline of HTTP requests and JSON transforms. There's nothing to build or deploy. Every run is recorded, and you can read, change, or pause a job in seconds.\u003C\u002Fp>\n\u003Ch2 id=\"why-now\">\u003Ca class=\"anchor\" href=\"#why-now\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Why now\u003C\u002Fh2>\n\u003Cp>More and more code is written by AI agents. Agents are good at describing what should happen and when. They're worse at owning the infrastructure that makes it happen: picking a host, wiring up a scheduler, rotating secrets, and keeping it all alive after the conversation ends.\u003C\u002Fp>\n\u003Cp>So we built cronservices to be easy for an agent to use correctly. The API is small and documented in \u003Ca href=\"\u002Fopenapi.json\">OpenAPI\u003C\u002Fa>. The docs are published as plain Markdown and \u003Ca href=\"\u002Fllms.txt\">llms.txt\u003C\u002Fa>. The \u003Ca href=\"\u002Fagents\">agent guide\u003C\u002Fa> says plainly when cronservices is the right tool and when it isn't. An agent can schedule work in one API call, and a person can see and change exactly what it did.\u003C\u002Fp>\n\u003Ch2 id=\"what-we-believe\">\u003Ca class=\"anchor\" href=\"#what-we-believe\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>What we believe\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Configuration beats code for glue.\u003C\u002Fstrong> If a task can be described as "fetch this, reshape it, send it there", it shouldn't need a deploy.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Small and predictable.\u003C\u002Fstrong> One scheduler, standard 5-field cron in any time zone, a template language you can learn in five minutes, and limits that are written down. No surprises at 3 a.m.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Readable by people and machines.\u003C\u002Fstrong> Every page on this site has a Markdown twin. If an agent can't read our docs, they aren't good enough.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Honest about limits.\u003C\u002Fstrong> Requests time out after 10 seconds. Templates don't branch or loop with side effects. When you need more than that, write the code and let cronservices call it.\u003C\u002Fp>\n\u003Ch2 id=\"get-started\">\u003Ca class=\"anchor\" href=\"#get-started\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Get started\u003C\u002Fh2>\n\u003Cp>\u003Ca href=\"\u002Flogin#signup\">Create a free account\u003C\u002Fa>, read the \u003Ca href=\"\u002Fdocs\">docs\u003C\u002Fa>, or point your coding agent at \u003Ca href=\"\u002Fllms.txt\">https:\u002F\u002Fcron.services\u002Fllms.txt\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"contact\">\u003Ca class=\"anchor\" href=\"#contact\" aria-hidden=\"true\" tabindex=\"-1\">#\u003C\u002Fa>Contact\u003C\u002Fh2>\n\u003Cp>Questions and account help: \u003Ca href=\"mailto:support@cron.services\">support@cron.services\u003C\u002Fa>.\u003C\u002Fp>\n",[6,9,12,15],{"id":7,"html":8},"why-now","Why now",{"id":10,"html":11},"what-we-believe","What we believe",{"id":13,"html":14},"get-started","Get started",{"id":16,"html":17},"contact","Contact",1793404039588]