InsideOut

What LocalMark checked

• Published Agent Card

  Inspect the source card ↗. The last successful fetch was 14 Nov 2026, 11:07 UTC.

• Latest card check: passed

  14 Nov 2026, 11:07 UTC · Agent Card validated

• Advertised endpoint: TLS connection passed

  14 Nov 2026, 11:07 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.

• Read-only protocol probe: JSON-RPC response received

  14 Nov 2026, 05:06 UTC · JSON-RPC response received; A2A behavior not confirmed LocalMark sent no message and did not request task creation.

• Unsigned card

  This card does not provide a digital signature. Checked 14 Nov 2026, 11:07 UTC.

• 30-day card check history

  537 of 539 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.

• Publisher claim

  No publisher claim has been completed for this listing.

Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.

Recent card checks

Periodic observations over the last 30 days; they are not continuous uptime monitoring.

View the 30-day check log as JSON →

Declared skills 4

• Cloud architecture design and Terraform generation

  Chat with Riley to design AWS or GCP infrastructure. Each turn returns the reply on the task and moves it to input-required. When the design changes, the task carries an infrastructure-ir artifact (the components), a cost-estimate artifact (monthly pricing) and, once Terraform is generated, a terraform-archive artifact with a download URL; task.metadata.terraform_ready turns true. Continue the conversation by sending messages with the same taskId and X-A2A-Task-Secret header.

  cloud architectcloud architecturedesignterraformiacinfrastructure-as-codecost-estimateawsgcp
• Cloud architecture design, Terraform generation, and deployment

  End-to-end conversational flow: describe an application and Riley designs the AWS or GCP infrastructure, estimates cost, generates downloadable Terraform (infrastructure-as-code / IaC), connects cloud credentials, deploys via managed Oracle, and streams deployment logs. Spans compute, databases, networking, storage, containers, Kubernetes, serverless, security, monitoring, and DevOps. The design-cloud-architecture, connect-cloud-credentials and deploy-infrastructure skills describe each step.

  cloud architectcloud architectureinfrastructureiacinfrastructure-as-codeterraformawsgcpdevopsdeploymentcost-estimatedatabaserdscloud-sqlpostgreskuberneteseksgkeecscontainers
• Cloud credential connection

  When a deploy finds no usable AWS or GCP credentials, the chat-task moves to auth-required and carries an aws-connect-link or gcp-connect-link artifact with the URL the user opens to attach credentials. After the user finishes, send any message to the same task: the executor re-checks credentials and retries the deploy.

  credentialsawsgcpauth-requiredconnect
• Terraform deployment

  Deploys the designed Terraform through the managed Oracle service. Once task.metadata.terraform_ready is true, confirm on the chat-task with metadata {"action":"deploy"}, or with a message whose whole text is "deploy", "yes deploy" or "go ahead ... deploy". The task moves to working and carries a deployment-job artifact with job_id and a stream_url for the deployment logs. Missing credentials divert to the connect-cloud-credentials flow.

  deploymentdeployterraformawsgcplogs