{"uid":"cap_FbLEpxzpe2MonNHTsw3sI","slug":"halowerk-sicherwerk-pkcs-12-certificate-trust-store-builder-cc9f43c4","name":"HALOWERK sicherwerk PKCS#12 Certificate Trust Store Builder","description":"Builds a PKCS#12 container holding certificates only, for the common case where a runtime insists on PKCS#12 as its trust store format. The password is explicitly empty and reported back as such, so nothing depends on an undocumented default, and the reply states outright that the store contains no private keys. That matters: a PKCS#12 file is the usual carrier for a key, and a consumer must be able to tell a trust store from an identity store without opening it.","url":"https://sicher.halowerk.com/v1/oss-openssl-pkcs12-certificate-store-build?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"certificates_pem":{"type":"array","items":{"type":"string","maxLength":262144,"minLength":1},"maxItems":16,"minItems":1}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_165wSBB4rNT_qh_7ZuRBa","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Builds a PKCS#12 trust store container from one or more PEM certificates, explicitly with no private keys and an empty password","exampleAgentPrompt":"I need to bundle these PEM certificates into a PKCS#12 trust store — no private key, empty password — so my Java runtime will accept it: [paste PEM certs here].","exampleUseCases":[{"title":"Java runtime TLS trust store setup","prompt":"My Java application requires a PKCS#12 trust store to validate TLS connections. Can you take these three CA PEM certificates and build a .p12 trust store for me with no private keys and an empty password?"},{"title":"Containerized service certificate packaging","prompt":"I need to ship our internal CA cert chain to a microservice that only accepts PKCS#12 format. Can you wrap these two PEM certs into a PKCS#12 file with no private key so it's clear it's a trust store and not an identity store?"},{"title":"Cross-platform certificate distribution","prompt":"We have several root and intermediate CA certificates in PEM format and need to distribute them as a single PKCS#12 trust store bundle to our Node.js and .NET services. Can you package up to five of these PEM certs into one .p12 file with an empty password and confirm there are no private keys inside?"}],"resultDescription":"A PKCS#12 (.p12) binary container holding only the supplied certificates (no private keys), with an explicitly empty password. The response also states the password is empty and confirms the absence of private keys, so consumers can reliably distinguish this trust store from an identity store without inspecting the file contents.","failureModes":["Invalid or malformed PEM certificate input causes rejection","Exceeding 16 certificates in the array returns an error","Empty array or missing certificates_pem field fails validation","Certificate PEM strings that are private keys or CSRs rather than certificates may be rejected","Oversized individual PEM strings beyond 262144 characters are rejected"],"whenToPreferThis":"Choose this endpoint when a runtime or platform strictly requires PKCS#12 format for its trust store and you only have PEM certificates (no private key). It is specifically designed for the trust-store use case (certificates only, empty password, explicit no-private-key declaration), making it safe and unambiguous for runtime consumption. Prefer it over manually invoking OpenSSL when you need a reproducible, auditable, zero-configuration conversion with a clear attestation that no private key material is present.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-29T00:32:42.662Z","isFirstParty":false,"canonicalSlug":"halowerk-sicherwerk-pkcs-12-certificate-trust-store-builder-cc9f43c4"}