How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ARCNM

ARCNM (legal name rattle mng GmbH) provides physics‑first should‑cost calculations for manufactured parts. By uploading a STEP model or CAD drawing the service extracts features, simulates process planning, and returns detailed cost breakdowns across lot sizes. It combines physics‑based manufacturing simulation with AI‑driven drawing interpretation, delivering auditable cost data for CNC milling, turning, sheet‑metal, additive manufacturing and more. The platform offers a REST API and MCP server for integration with ERP, PLM, and quoting workflows.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles ARCNM the way a machine reads it — 31 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ARCNM scores 42.8/100 (developing), with a separate agent-readiness read of 47/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
ARCNM Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from ARCNM's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/arcnm-io/"
   title="ARCNM on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/arcnm-io.svg"
       alt="ARCNM Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile ARCNM

Each block below is one kind of artifact we hold for ARCNM. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 17

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

ARCNM Calculations API

The calculations API from ARCNM — 42 operation(s) for calculations.

ARCNM Calibration API

The calibration API from ARCNM — 18 operation(s) for calibration.

ARCNM Datasets API

The datasets API from ARCNM — 3 operation(s) for datasets.

ARCNM Environments API

The environments API from ARCNM — 33 operation(s) for environments.

ARCNM Folders API

The folders API from ARCNM — 5 operation(s) for folders.

ARCNM Geometry API

The geometry API from ARCNM — 2 operation(s) for geometry.

ARCNM Import API

The import API from ARCNM — 4 operation(s) for import.

ARCNM Machine Library API

The machine-library API from ARCNM — 4 operation(s) for machine-library.

ARCNM Machines API

The machines API from ARCNM — 2 operation(s) for machines.

ARCNM Materials API

The materials API from ARCNM — 22 operation(s) for materials.

ARCNM Nesting API

The nesting API from ARCNM — 13 operation(s) for nesting.

ARCNM Parts API

The parts API from ARCNM — 8 operation(s) for parts.

ARCNM Remnants API

The remnants API from ARCNM — 5 operation(s) for remnants.

ARCNM Subcontractors API

The subcontractors API from ARCNM — 3 operation(s) for subcontractors.

ARCNM Tools API

The tools API from ARCNM — 11 operation(s) for tools.

ARCNM Upload Links API

The upload-links API from ARCNM — 2 operation(s) for upload-links.

ARCNM Uploads API

The uploads API from ARCNM — 10 operation(s) for uploads.

Scroll within the panel for all 17 ·

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Arcnm Io Rate Limits

4 limits

RATE LIMITS

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Arcnm Io Context

120 classes · 514 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

ARCNM API Rules

54 rules · 42 errors · 10 warnings

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

CalculationCreate

20 properties

JSON SCHEMA

CalculationDetailResponse

49 properties

JSON SCHEMA

CalculationTuningUpdate

34 properties

JSON SCHEMA

EnvironmentDetail

45 properties

JSON SCHEMA

EnvironmentEconomicsUpdate

24 properties

JSON SCHEMA

UploadAndQuoteJSON

30 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Arcnm Io Authentication

2 schemes

SECURITY

Arcnm Io Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Arcnm Io Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Arcnm Io Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Arcnm Io Agentic Access

245 operations · 154 acting · 11 human-in-the-loop

245 operations · 154 acting

AGENTIC

Resources

Every other property we hold for ARCNM — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/arcnm-io · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of ARCNM, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.