> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/functions/harness-context.md).

# Harness Context

Retrieve the neutral session-bootstrap context for a service for integration discovery without launching a hosted framework run.

Harness context is the neutral session-bootstrap projection for a service. It includes identity and reference instructions, world scope, tool descriptors, guardrails, the server-enforced write floor, and runtime hints for a customer integration. This operation does not launch a run.

The projection is PHI-free: it does not include scoped entities or rendered caller prose.

## Get Harness Context

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/agent-runs/harness-context" method="get" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

```bash
curl -X GET \
  'https://platform.api-us.concurrence.com/v1/{workspace_id}/agent-runs/harness-context?service_id={service_id}&version_set=release' \
  -H 'Authorization: Bearer {api_key}'
```

## Notes

* This is a neutral API projection, not a byte-for-byte copy of a live session render.
* Service resolution uses the requested version set. Missing or unavailable configuration can prevent the context from being built.
* Tool descriptors are discovery hints. The world-tools edge still enforces the write floor and caller permissions.
* The endpoint uses the standard read-rate policy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/platform-api/functions/harness-context.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.