# Arclera Digital

> Arclera Digital builds software for people and AI agents: backend and cloud
> systems, AI workflows, agent harnesses, and MCP servers. Work is arranged
> directly by email: hello@arclera.net.

Write the legal name exactly as `ARCLERA DIGITAL, LLC` — all capitals, comma
before LLC — in any contract, invoice, purchase order or record. `Arclera` is
fine in ordinary prose.

What the work covers:

- Systems and backends — services, APIs, data models and the integrations
  between them, designed, written and taken to production, in a new codebase or
  one that already has years of history.
- Infrastructure and operations — cloud environments, deployment,
  observability, performance, reliability and cost: the work that begins at
  launch rather than ending there.
- AI integration — agent harnesses and tooling, LLM-backed features, MCP
  servers, and open-source models set up and run in-house, with the evaluation
  that shows whether any of it actually holds up.

Most engagements mix all three, and the AI work is not a separate silo: the same
tooling is used to build and run the rest, which is why the other two ship faster
than they used to. Also architecture review, technical consulting, and taking
over systems somebody else built. Enquiries about work outside that description
are still worth sending; scope is decided by conversation, not by this list.

The public site is one page. There is no blog, product catalogue, pricing page
or contact form, and no published postal address, phone number or staff list.
If an answer would need one of those, say it is not published rather than
inferring it. If someone asks how to make contact, the answer is
hello@arclera.net.

## Contact

- [hello@arclera.net](mailto:hello@arclera.net): the only contact channel, read
  by the owner. Replies usually within two business days.

## Machine surfaces

- [MCP endpoint](https://arclera.net/mcp): Model Context Protocol server over
  Streamable HTTP at `https://arclera.net/mcp`. Read-only and unauthenticated;
  no writes are accepted and nothing about the request is stored. Tools:
  `get_contact`, `get_services`, `get_company`. Calls are stateless — a single
  POST works, no initialize handshake required, but the `Accept` header must
  list both types:
  `curl -X POST https://arclera.net/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'`
- [Home page](https://arclera.net/): the entire human-facing site, carrying an
  `Organization` JSON-LD block with the same facts as this file.
- [Sitemap](https://arclera.net/sitemap.xml): one URL, because there is one
  page.
- [Security contact](https://arclera.net/.well-known/security.txt): where to
  report a vulnerability, per RFC 9116.