Tag: infrastructure
All the articles with the tag "infrastructure".
-
Open Data Wasn't Missing. The Interface Was.
A 12-domain benchmark and Sentinel-2 experiment show where the Registry of Open Data MCP server works, where search fails, and what the interface unlocks.
-
Every Way to Attribute Cost on Amazon Bedrock, Live-Tested
A working map of every mechanism Amazon Bedrock has for attributing inference cost — resource tags, identity tags, and request metadata — with config examples, and where SaaS billing has to leave the AWS billing layer entirely.
-
Prompt Caching Is a Harness Design Problem, Not Just an API Toggle
A 186-request test shows why cache savings depend on stable tools, deterministic prefixes, deliberate breakpoints, routing keys, and measurement inside the agent harness.
-
Two Ways to Authorize an Agent Tool: IAM or OAuth on Amazon Bedrock AgentCore Gateway
When you expose a tool to agents through an AgentCore Gateway, the real decision is who is allowed to call it — SigV4/IAM for callers inside your AWS boundary, or a JWT authorizer for everyone else. Here are the three patterns and when each fits.
-
Zed on Bedrock Makes the Agent Harness Portable
Wiring Zed to Amazon Bedrock turns Zed's agent harness into a provider-portable coding surface across the frontier models your account can reach.
-
Agent Sprawl Is a Skills Problem
I had hundreds of skills scattered across agent harnesses, repos, and drafts folders. No single view of what existed, what was current, or what was actually wired in. The market is hitting the same wall.
-
Your Agent Doesn't Need the Secret. It Needs the Result.
Vault-backed credentials are the floor for agent security, not the ceiling. The pattern converging across 2026 security research goes further: scope vaults to the task, expire tokens with the task, and broker credentials so the agent never holds one at all.
-
How This Site Is Built
Updated:The stack behind artificialcuriositylabs.ai: Astro on S3 + CloudFront, DNS on Cloudflare, email forwarding via SES, and an AI-readable content layer. Every decision explained.